job matching for migrants (2)

Job Matching For Migrants J Kiran Kumar

Reg No: 2608111

Job Matching For Migrants


Reg No: 2608111

1.1 AIM:

Job Matching for Migrants is an online based web application system to

handle non formal jobs. This system deals with the Universal ID based

posting of informal sector jobs for illiterate or migrant users/laborers.

Simulation of service provided by Ministry of Human Resources. This system

facilitates employers to engage labors easily and also it helps to assisters in

the local area to maintain migrant laborers details based on Universal ID.

Users of this system; assisters and employers should be register, then

he/she can maintain the data about his/her company. Assisters can also

store the details of the laborers on his/her hand. This system also provides

the email communication among the users of this system.

Scope:

Ø System should give the facility to know about the system before register

into the system.

Ø And the general user can see the members in this system.

Ø System should facilitate to register into this system with different roles

like Assister and Employer.

Ø Any user login into the system through one user interface only, this

system should identify the role of the user and it must show the

corresponding user home page based on role.

Ø System must provide the option to Assister to store laborers details on

her/his hand.

Ø And it should provide the facility like update and delete labors details.

Ø Users can communicate with each other through mailing.

Ø Employer can see the details of labors hired by him/her.


Reg No: 2608111

1.2 Purpose of the project:

• It is a universal id based informal works for labours.

• Providing labour details to the employers.

• Providing works to the labours.

• Reducing work cost and time to finding the labours because it is

completely online.

1.3 Problem in existing system:

Existing System

• It is manual system.

• Complexity in maintaining large number of data about laborers.

• The existing system can’t provide the Universal ID based posting of

informal jobs for laborers.

• Communication between assisters and employers is not much better in

existing system.

• Viewing of laborers details and skills to employers is toughest thing in

existing system.

• Existing system does not provide the security for the labors details.

• There is no proper registration for existing system.

1.4 Solutions for these problems:

The best solution is making it completely online and computerized. The

benefits are:

§ The purpose of computerised is storing and retrieving details of

labours are very easy.

§ Then making it completely online so providing more flexibility for

accessing their details will become simpler.


Reg No: 2608111

§ The person who maintains the details of the labours called assistor

should entire their details by registering them into system (Jobs

matching for migrants).

§ So from every location if the assistor registers the details of labours

then accessing and checking their status will become easy.

§ Then if someone needs labour then they should register with us called

as employee.

§ Finally the employee will search the labours as per their requirements

and then same will be informed to the particular area assistor, such

that assistor will fulfill their requirements.


Reg No: 2608111

System Analysis


Reg No: 2608111

2.1 STUDY OF THE SYSTEM

In the flexibility of uses the interface has been developed a graphics

concepts in mind, associated through a browser interface. The GUI’s at

the top level has been categorized as follows

1. Administrator Interface Design.

2. User Interface.

3. Security Authentication.

4. Reports.

5. General end-users.

The administrative user interface will maintain the different users details, the

interface helps the administration with all the transactional states like which

users sending the mails, and which users receiving whishing mails, users

details information history. And the statistics of the system in difference

strategies.

NUMBER OF MODULES

The system after careful analysis has been identified to be presented

with the following modules:

The Modules involved are

1. Admin module

2. Assister module

3. Employer module

4. Mailing module

5. General user module

6. Security and authentication module

7. Report module

8. Registration Module.


Reg No: 2608111


Reg No: 2608111

MODULES DESCRIPTION

Module description for each module mention on top

1. Admin Module:

Ø Admin should also login to the system. Ø Admin can see the user details of this system like assisters and

employers. Ø And also he can monitor the movements of the users. Ø And the admin can delete the account of any user.

2. Assister Module:

This module is for assisters ,who is willing provide professional or expert advice in particular area of expertise such as constructions and cultivating and digging.

Assister module can be divided into three sub modules.

Ø Maintaining labors module. Ø Updating labor profile module. Ø Show the labor profile to Employer.

§ Maintaining labors module:

In this module the assister has to maintain the details of local

labor like crime, personal and previous employment history. Every labor can get the unique Universal ID after inserted into the system successfully. The labor can later register any location by using this ID.

§ Updating labor profile module:

In this module the assister can update/modify the labor details any where through this system by using Universal ID.

§ Show the labor profile to Employer:

In this module the assister can give the permission to the

employer to view the details of the particular labors hired by the

employer. And also the assister can send the mail to the employer by

specifying his commission.


Reg No: 2608111

3. Employers Module:

In this specified module the employer is able to send request to local assisters by specifying his/her requirement through mailing. He/she can see details of laborers like their skills, languages spoken, previous employment history and etc... Those are hired by him from the assister. He/she can search for assisters in local area.

4. General User Module:

In this module the general user can visit this website and also he can see the benefits and services provided by this system without login into the system. This system allows the general user to view employers and assister in this system.

5. Mailing Module:

In this module the employer can search for an assister in the local area. And also the employer can communicate with the assister in local area by sending mail. He should specify his requirements via mail. According to employer requirements, the assister may reply to the employer by sending labors list.

6. Security and Authentication Module:

This module the security for an user data. And this system prevents the unauthorized access from the unauthorized person. This can only allows the authorized users only. Data is stored in a secure manner.

7. Report Module:

In this module the system Is able to view the data, which is coming from the database in a tabular format. This may help the user to understanding easily.

8. Registration Module:

ü Assistor: When assistor registers then assistor can manage/add labours.

Such that assistor can get security for their data.

ü Employer: Employer should register in the system and then we are going

to provide the assistor details and their respective labour details.

Through registration Assistor can enter labour details and Employer

can search for assistors and their labours.


Reg No: 2608111

Users of This System:

Ø Assisters Ø Employers Ø Labors Ø General user Ø Administrator

Assisters:

Assister should register into this system, and also he/she can choose

his/her own user name and password. After login to the system the assister

can view/update his company profile and also he can store the crime and

personal, previous employment details of the available labors in the local

area, this system provides the unique Universal ID for each entered labor by

the assister. Later this ID is serves to modify the labor details.

Employers:

Employer should register into this system, and also he/she can choose

his/her own user name and password. After he/she login to the system,

he/she can view/update his/her profile. And this system provides the facility

to search for a local assister by entering area name. The employer can send

his/her requirements to the local assisters through mail. Employers can also

view the crime details and personal details of the labors hired by him/her

before pay the money to assister.

Labors:

Labors are consumers of this system. Labors details are maintained by

the assisters. Each labor can get unique Universal ID; he/she can later

register any location by using this ID.

General user:

General user can see the services provided by this system and also the

general user can see the registered employers and assisters. If he/she

wants, he/she can register.

Administrator:


Reg No: 2608111

Administrator can also view the employers and assisters details and the admin can monitor the users of this system. He can also delete the account. 2.2 Proposed System

The development of this new system contains the following activities, which try to automate the entire process keeping in the view of database integration approach.

• Automates information related to Assisters, Employer and Laborers.

• Allows Assisters to maintain complete and accurate details about local

laborers by using Universal ID.

• This Universal ID Facilitates to laborers, he/she can later register or

use any other location and deployment.

• It provides facility to employers to see laborers bio-data and crime

details on laborer, those laborers were hired by the employers.

• This system provides the security for the labors details, those details

entered by the Assisters.

• This system prevents the un-authorized accessing.

• Rich user interface.

2.3 Process Model:

SDLC METHODOLOGIES

This document play a vital role in the development of life cycle (SDLC) as

it describes the complete requirement of the system. It means for use by

developers and will be the basic during testing phase. Any changes made

to the requirements in the future will have to go through formal change

approval process.

SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A

spiral Model of Software Development and Enhancement. This model was

not the first model to discuss iterative development, but it was the first

model to explain why the iteration models.


Reg No: 2608111

As originally envisioned, the iterations were typically 6 months to 2

years long. Each phase starts with a design goal and ends with a client

reviewing the progress thus far. Analysis and engineering efforts are

applied at each phase of the project, with an eye toward the end goal of

the project.

The steps for Spiral Model can be generalized as follows:

• The new system requirements are defined in as much details as

possible. This usually involves interviewing a number of users

representing all the external or internal users and other aspects of

the existing system.

• A preliminary design is created for the new system.

• A first prototype of the new system is constructed from the

preliminary design. This is usually a scaled-down system, and

represents an approximation of the characteristics of the final

product.

• A second prototype is evolved by a fourfold procedure:

1. Evaluating the first prototype in terms of its strengths,

weakness, and risks.

2. Defining the requirements of the second prototype.

3. Planning an designing the second prototype.

4. Constructing and testing the second prototype.

• At the customer option, the entire project can be aborted if the risk

is deemed too great. Risk factors might involved development cost

overruns, operating-cost miscalculation, or any other factor that

could, in the customer’s judgment, result in a less-than-satisfactory

final product.

• The existing prototype is evaluated in the same manner as was the

previous prototype, and if necessary, another prototype is

developed from it according to the fourfold procedure outlined

above.


Reg No: 2608111

• The preceding steps are iterated until the customer is satisfied that

the refined prototype represents the final product desired.

• The final system is constructed, based on the refined prototype.

• The final system is thoroughly evaluated and tested. Routine

maintenance is carried on a continuing basis to prevent large scale

failures and to minimize down time.

The following diagram shows how a spiral model acts like:


Reg No: 2608111

Fig 1.0-Spiral Model

ADVANTAGES

• Estimates(i.e. budget, schedule etc .) become more relistic as work

progresses, because important issues discoved earlier.


Reg No: 2608111

• It is more able to cope with the changes that are software

development generally entails.

• Software engineers can get their hands in and start woring on the

core of a project earlier.

2.4 System Architecture:

PROCESS FLOW ARCHITECTURE DIAGRAM

1. THE PRESENTATION LAYER

Also called as the client layer comprises of components that are

dedicated to presenting the data to the user.


Reg No: 2608111

For example: Windows/Web Forms and buttons, edit boxes, Text

boxes, labels, grids, etc.

2. THE BUSINESS RULES LAYER

This layer encapsulates the Business rules or the business logic of

the encapsulations. To have a separate layer for business logic is of a

great advantage. This is because any changes in Business Rules can be

easily handled in this layer. As long as the interface between the layers

remains the same, any changes to the functionality/processing logic in

this layer can be made without impacting the others. A lot of client-

server apps failed to implement successfully as changing the business

logic was a painful process.

3. THE DATA ACCESS LAYER

This layer comprises of components that help in accessing the

Database. If used in the right way, this layer provides a level of

abstraction for the database structures. Simply put changes made to

the database, tables, etc do not affect the rest of the application

because of the Data Access layer. The different application layers send

the data requests to this layer and receive the response from this layer.

4. THE DATABASE LAYER

This layer comprises of the Database Components such as DB

Files, Tables, Views, etc. The Actual database could be created using

SQL Server, Oracle, Flat files, etc.

In an n-tier application, the entire application can be implemented

in such a way that it is independent of the actual Database. For

instance, you could change the Database Location with minimal changes

to Data Access Layer. The rest of the Application should remain

unaffected.


Reg No: 2608111

FEASIBILITY


Reg No: 2608111

FEASIBILITY REPORT

3.1 TECHNICAL FEASIBILITY:

Evaluating the technical feasibility is the trickiest part of a feasibility

study. This is because, at this point in time, not too many detailed design of

the system, making it difficult to access issues like performance, costs on

(on account of the kind of technology to be deployed) etc. A number of

issues have to be considered while doing a technical

analysis.

i) Understand the different technologies involved in the proposed

system:

Before commencing the project, we have to be very clear about

what are the technologies that are to be required for the development

of the new system.

ii) Find out whether the organization currently possesses the

required technologies:

o Is the required technology available with the organization?

o If so is the capacity sufficient?

For instance –

“Will the current printer be able to handle the new reports and

forms required for the new system?”

3.2 OPERATIONAL FEASIBILITY:

Proposed projects are beneficial only if they can be turned into

information systems that will meet the organizations operating

requirements. Simply stated, this test of feasibility asks if the system will

work when it is developed and installed. Are there major barriers to

Implementation? Here are questions that will help test the operational

feasibility of a project:

§ Is there sufficient support for the project from management from

users? If the current system is well liked and used to the extent that


Reg No: 2608111

persons will not be able to see reasons for change, there may be

resistance.

§ Are the current business methods acceptable to the user? If they are

not, Users may welcome a change that will bring about a more

operational and useful systems.

§ Have the user been involved in the planning and development of the

project?

§ Early involvement reduces the chances of resistance to the system and

in .

§ General and increases the likelihood of successful project.

Since the proposed system was to help reduce the hardships

encountered. In the existing manual system, the new system was

considered to be operational feasible.

3.3 ECONOMIC FEASIBILITY:

Economic feasibility attempts 2 weigh the costs of developing and

implementing a new system, against the benefits that would accrue from

having the new system in place. This feasibility study gives the top

management the economic justification for the new system.

A simple economic analysis which gives the actual comparison of costs

and benefits are much more meaningful in this case. In addition, this proves

to be a useful point of reference to compare actual costs as the project

progresses. There could be various types of intangible benefits on account of

automation. These could include increased customer satisfaction,

improvement in product quality better decision making timeliness of

information, expediting activities, improved accuracy of operations, better

documentation and record keeping, faster retrieval of information, better

employee morale.


Reg No: 2608111

SOFTWARE REQUIREMENT SPECIFICATION


Reg No: 2608111

SOFTWARE REQUIREMENT AND HARDWARE REQUIREMENT

4.1 SOFTWARE REQUIREMENTS

Operating System : Windows XP/2003 or Linux

User Interface : HTML, CSS

Client-side Scripting : JavaScript

Programming Language : Java

Web Applications : JDBC, Servlets, JSP

IDE/Workbench : My Eclipse 6.0

Database : Oracle 10g

Server Deployment : Tomcat 5.x/6.x

4.2 HARDWARE REQUIREMENTS

Processor : Pentium IV Hard Disk : 40GB RAM : 1GB or more

job matching for migrants (2)

Documents