prjrpt

7/28/2019 prjrpt

1/27

A

Practical Training Seminar Report

On

Job Portel

Submitted in partial fulfillment

of requirement forDegree of Master

in Computer Science

2012-13

Submitted To: Submitted By:

Mr. Anita

Program Coordinator Roll No-

B.Tech.Computer Science Engineering EnrollmentNo-

Post Graduate Department of Computer Science Engineering

Suresh Gyan Vihar University

Mahal Jagatpura,Jaipur

7/28/2019 prjrpt

2/27

7/28/2019 prjrpt

3/27

Suresh Gyan Vihar University

Mahal Jagatpura,Jaipur

Certificate of Practical Training Seminar Report 2012-13

It is here to certify that Neeraj Lamba student of B.Tech. IV year (7th SEM)

Computer Science have submitted their report on Practical Training Seminar on Job

Portal.. In Partial fulfillment of Practical Training prescribed in the syllabus of

Suresh Gyan Vihar University (Jaipur) for B.Tech. Examination.

Gajanand Sharma

PTS In charge

Assistant Professor

CSE Department

7/28/2019 prjrpt

4/27

Index

7/28/2019 prjrpt

5/27

About the technology

7/28/2019 prjrpt

6/27

5. LITERATURE SURVEY

5.1 SURVEY OF EXISTING SYSTEM

Existing system work manually. The existing system has got lot of intricacies

within itself and need lot of human effort and paper works. All above the data need to be

maintained on ledgers and maintaining this is a tedious and risky process.

present system was not transparent much paper work was evolved there was

no interface for public viewing there was not enough time for purchasing or compare

price so buyer not have enough time to best deal. To view a data may need lot of paper

to be searched.

5.1.1 SOME DRAWBACKS OF EXISTING SYSTEM

Some of the negative aspects of the existing system are as follows:

1) Action is time consuming. Wherever a need for search arises, the process evolves

search through paper records.

2) So many products in the market so user is much confused.

3) Paper records are easily damaged in course of time. The life time of paper record is

unreliable less that it easily gets spoiled.

4) Manual system needs added man power.

5) Prone to corruption by unauthorized users. Securing of manual system is not fully

guaranteed. Inaccuracy can be expected. Data can get easily scratched.

5.2 STUDY OF IMPLEMENTED SYSTEM

There was bulk amount of data from different institutions each having its own data

no centralization candidate has limited time period and limited options handling of this

large data was a major problem faced single view was available for everyone. Much

paper work was involved. Hence a Centralization of information was required to

reduce paper work and Simplify operating procedures.

Key Questions:

What is being done?

How is it being done?

7/28/2019 prjrpt

7/27

How frequent does it occur?

How great is the volume of decisions?

How well is the task being performed?

Does a problem exist?

If problems exist, how serious is it?

If a problem exists, what is the underlying cause?

6. PROBLEM STATEMENT

Problem Statement tells about the problem with existing system. Here are some key

problems are described below:

1) Existing system work manually. The existing system has got lot of intricacies within

itself and need lot of human effort and paper works. All above the data need to be

maintained on ledgers and maintaining this is a tedious and risky process.2) present system was not transparent much paper work was evolved there was

no interface for public viewing there was not enough time for purchasing or

compare price so buyer not have enough time to best deal. To view a data may

need lot of paper to be searched.

7. PROBLEM ANALYSIS

7.1 PLANNING

The key to a successful project is in the planning. Creating a project plan is

the rst thing you should do when undertaking any kind of project.

7.1.1 PROJECT GOALS

A project is successful when the needs of the stakeholders have been met. A

stakeholder is anybody directly, or indirectly impacted by the project. The Goal of our

project is to develop a user friendly Alumni Website.

7/28/2019 prjrpt

8/27

7.1.2 PROJECT DELIVERABLES

Website

SourceCode

A

Project

Report

7.1.3 PROJECT SCHEDULE

Planning and requirement analysis

phase 5 days Design phase 15

days

Co

din

g

20

da

ys

Te

sti

ng5

da

ys

7.2 PROJECT REQUIREMENTS

Operating System: Windows 7/Windows 8,Windows XP

Software: Website BrowserAdobe Dreamweaver CS 5, Wamp, My SQL,SQL, Xampp

Hardware: Core 2 Duo Processor, RAM 2GB and Hard-disk 320 GB.

7.3 REQUIREMENT ANALYSIS

7.3.1 FUNCTIONAL REQUIREMENTS

The various features or functional requirements are:

The administrator can verify registrations of the new users.

7/28/2019 prjrpt

9/27

The administrator can also block or activate users account.

The administrator can specify news and events.

The buyer can purchase product,add product request give there feedback aftersuccessful logging in to the project.

The user can also send there billing details.

7.3.2 NON-FUNCTIONAL REQUIREMENTS

1. Secure access of con entail data.

2. 24 X 7 availability.

3. Better component design to get better performance at peak time.

4. Flexible service based architecture will be highly desirable for future

extension.

7.4 FEASIBILTY ANALYSIS

A feasibility study is conducted to select the best system that meets performance

requirement. This entails an identification description, an evaluation of candidate

system and the selection of best system for the job. The system required performance is

defined by a statement of constraints, the identification of specific system objective and

a description of outputs.

The key consideration in feasibility analysis are

1. Economical Feasibility

2. Technical Feasibility

3. Operational Feasibility

7.4.1 OPERATIONAL FEASIBILITYThe system will be used if it is developed well then be resistance for users that

undetermined. No major training and new skills are required as it is based on DBMS

model. It will help in the time saving and fast processing and dispersal of user request

and applications. New product will provide all the benefits of present system with

better performance. User involvement in the building of present system is sought to

keep in mind the user specific requirement and needs. User will have control over their

own information. Important information such as pay-slip can be generated at the click

of a button. Faster and systematic processing of user application approval, allocation of

IDs, payments, etc. used had greater chances of error due to wrong information entered

by mistake

7.4.2 TECHNICAL FEASIBILITY

7/28/2019 prjrpt

10/27

It is a measure of the practically of a specific technical solution and the

availability of technical resources and expertise. The proposed system uses PHP as

front-end and MySQL as back-end tool. MySQL is a popular tool used to design and

develop database objects such as table views, indexes. The above tools are readily

available, easy to work with and widely used for developing commercial application.

Hardware used in this project are- p6 processor 2.0GHz, 2 GB RAM, 40 GB

hard disk, floppy drive. This hardware was already available on the existing computer

system. The software like MySQL, Thin Driver, Web Browser and operating system

WINDOWS-7 used were already installed On the existing computer system. So no

additional hardware and software were required to purchase and it is technically

feasible. The technical feasibility is in employing computers to the organization. The

organization is equipped with enough computers so that it is easier for updating.

Hence the organization has not technical difficulty in adding this system.

like MySQL, Thin Driver, Web Browser and operating system WINDOWS-7 used

were already installed On the existing computer system. So no additional hardware

and software were required to purchase and it is technically feasible. The technical

feasibility is in employing computers to the organization. The organization is

equipped with enough computers so that it is easier for updating. Hence the

organization has not technical difficulty in adding this system.

Tools Used :

PHP MySQL

Ajax

Xampp Server

7.4.3 ECONOMIC FEASIBILITY

It looks at the financial aspects of the project. It determines whether the

management has enough resources and budget to invest in the proposed system and

the estimated time for the recovery of cost incurred. It also determines whether it is

worthwhile to invest the money in the proposed project. Economic feasibility is

determines by the means of cost benefit analysis. The proposed system is

economically feasible because the cost involved in purchasing the hardware and the

software are within approachable. The personal cost like salaries of employees hired

are also nominal, because working in this system need not required a highly qualified

professional.

The operating-environment costs are marginal. The less time involved also

helped in its economical feasibility. It was observed that the organization has already

using computers for other purpose, so that there is no additional cost to be incurred foradding this system to its computers.

7/28/2019 prjrpt

11/27

The backend required for storing other details is also the same database that is

MySQL. The computers in the organization are highly sophisticated and dont needs

extra components to load the software. Hence the organization can implement the new

system without any additional expenditure. Hence, it is economically feasible.

8. PROJECT DESIGN

8.1 HIGH LEVEL DESIGN

A high-level design provides an overview of a solution, platform, system,

product, service, or process. Such an overview is important in a multi-project

development to make sure that each supporting component design will be compatible with

its neighboring designs and with the big picture.

The highest level solution design should brie y describe all platforms, systems,

products, services and processes that it depends upon and include any important

changes that need to be made to them.A high-level design document will usually

include a high-level architecture diagram depicting the components, interfaces and

networks that need to be further speci ed or developed.

The document may also depict or otherwise refer to work ows and/or data

ows between com-ponent systems.In addition, there should be brief consideration of all

signi cant commercial, legal, environmental, security, safety and technical risks, issues

and assumptions.

The idea is to mention every work area brie y, clearly delegating the ownership of more

detailed design activity whilst also encouraging e ective collaboration between the various project

teams.Today, most high-level designs require contributions from a number of experts,

representing many distinct professional disciplines.Finally, every type of end-user should be

identi ed in the high-level design and each contributing design should give due consideration

to customer experience.

7/28/2019 prjrpt

12/27

DFD

Level 0 Diagram for Jobbing Portcullis :

User User Jobbing

Portcullis Output

Level 1 Diagram for Admin:

AdminValid ID &Password

Seekers

Employers

Job Fair

CompanyDetails

Logout

Id&password

VIEW

ADD &VIEW

VIEW

DB

Invalid Id&password

SIGNOUT

VIEW

7/28/2019 prjrpt

13/27

Level 1 Diagram for Job seeker:

Job Seekers Valid ID &Password

ViewJobs

SearchJobs

Jobfairs

Account

Logout

Id&password

ViIEW

VIEW

View &Update

DB

Invalid Id&password

VIEW

SIGNOUT

Registration

INPUT

Level 1 Diagram for Employer:

7/28/2019 prjrpt

14/27

EmployerValid ID &Password

Account

SearchResumes

Post Jobs

Logout

Id&passwordVIEW

DB

Invalid Id&password

Registration

Input

Search

Level 2 Diagram for Admin:

7/28/2019 prjrpt

15/27

Admin

Seekers

Employers

Job Fair

CompanyDetails

View

Employer

DeleteEmployer

VIEW

Date

Location

Functionalarea

ADD

VIEW

SeekerDetails

EmployerDetails

Job Fair Details

Company Details

SAVE TO DB

SAVE TO DB

SAVE TO DB

SAVE TO DB

VIEW&DELETE SAVE TO DB

SAVE TO DB

SAVE TO DB

SUCCESS OR FAILURE

SUCCESS OR FAILURE

SUCCESS ORFAILURE

SUCCESS OR FAILURE

SUCCESS OR FAILURE

SUCCESS OR FAILURE

SUCCESS OR FAILURE

Level 2 Diagram for Job seeker:

7/28/2019 prjrpt

16/27

Job Seeker

Registration

Jobs

Job Fiar

Account

SearchJobs

SavedJobs

AppliedJobs

ViewJobs

Area

Experience

PostResume

Input

sends

Job Details

SeekerDetails

Resume Details

Job Fair Details

SAVE TO DB

SUCCESS OR FAILURE

SAVE TO DB

SUCCESS OR FAILURE

SAVE TO DB

SUCCESS OR FAILURE

SUCCESS OR FAILURE

Seeker Details

View

Search

View

Update

SAVE TO DB

SAVE TO DB

SAVE TO DB

SAVE TO DBSAVE TO DB

Level 2 Diagram for Employer:

7/28/2019 prjrpt

17/27

Employer

Registration

Account

Resumes

Post

Input

View

Posting

FunctionalArea

Experience

Interviewdate

CompanyName

EmployerDetails

AccountDetails

SeekerResume Details

POsting job

Details

SUCCESS OR FAILURE

SAVE TO DB

SAVE TO DB

Search

SAVE TO DB

Update

search

SUCCESS OR NOT

SUCCESS OR NOT

SUCCESS OR NOT

SUCCESS OR NOT

SUCCESS OR FAILURE

SAVE TO DB

SAVE

SAVE

Search

7/28/2019 prjrpt

18/27

ERD

DB DESIGN:

Entities:

1. Admin

2. Job fair

3. Job details

4. Company Details

5. Seeker Details

6. Post Resume

7. Employer Details

Entities with Attributes:

1.Admin :

User Id

Password

2.Job fair:

Interview date

Location

Functional area

3.Job details:

Job id Job code

Job description

Posted date

Interview date

Functional area

Key skills

Experience

Contact number

Email id

Location

4.Company details:

Company id

Company name

Company website

Company information

Company email id

Company contact number

Company Address

5.Seeker details:

7/28/2019 prjrpt

19/27

Seeker id

Password

First name

Last name

Email id

Security question

Security answer

Contact number

Job id

Status

6.Post Resume:

First name

Last name

Email id

Functional area

Experience Annual salary

Key skills

Resume path

Resume headline

Basic qualification

7.Employer details:

Employer id

Password

First name

Last name

Email id

Location

Company id

Status

HasAdmin Employer

7/28/2019 prjrpt

20/27

Has

EmployerID(PK)

Password

FirstName

LastName

EmailID

Location

CompanyID(FK)

Status

Admin ID (PK)

Password

Admin ID (PK)

Password

CompanyID(PK)

CompanyName

CompanyWebsite

CompanyInformation

CompanyEmailID

ContactNo

CompanyAddress

SeekerID

AdminCompany

SeekerDetails JobDetailsHas

7/28/2019 prjrpt

21/27

SeekerName

JobID(PK)

SeekerEmailID

ContactNo.

jobID(FK)

JobDetails

KeySkills

SeekerEmailID

ContactNo.

InterviewDate

FunctionalArea

EmployerID(PK)

Password

FirstName

LastName

EmailID

Location

CompanyID(FK)

Status

CompanyID(PK)

CompanyName

CompanyWebsite

CompanyInformation

CompanyEmailID

ContactNo

CompanyAddress

SeekerID

SeekerName

JobID(PK)

Company EmployerHas

JobSeekersEmployers

Has

7/28/2019 prjrpt

22/27

Data Dictionary:

Admin:

SeekerEmailID

ContactNo.

EmployerID(FK)

EmployerID(PK)

Password

FirstName

LastName

EmailID

Location

CompanyID(FK)

Status

SNO COLUMN NAME DATA TYPE

(SIZE)

CONSTRAINTS

(KEY)

REFERENCES

FROM

7/28/2019 prjrpt

23/27

Job Seekers:

Employer Details:

1 ADMINID VARCHAR(15) PRIMARY KEY

2

PASSWORD VARCHAR(15) NOTNULL


(SIZE)

CONSTRAINTS

(KEY)

REFERENCES

FROM1 SEEKER_ID INT(10) PRIMARY KEY

2USERNAME VARCHAR(15) NOTNULL

3. PASSWORD VARCHAR(15) NOTNULL

4. FIRSTNAME VARCHAR(15) NOTNULL

5. LASTNAME VARCHAR(15) NULL

6. EMAILID VARCHAR(15) NOTNULL

7. SECURITY_QUESTION VARCHAR(15) NOTNULL

8. SECURITY_ANSWER VARCHAR(15) NOTNULL

9. COUNTRY VARCHAR(15) NOTNULL

10 LOCATION VARCHAR(15) NOTNULL

11 CONTACT_NUM VARCHAR(15) NOTNULL


(SIZE)

CONSTRAINTS

(KEY)

REFERENCES

FROM

7/28/2019 prjrpt

24/27

Job Details:

1 EMPLOYER_ID INT(10) PRIMARY KEY

2

USERNAME VARCHAR(15) NOTNULL

3. PASSWORD VARCHAR(15) NOTNULL

4. FIRSTNAME VARCHAR(15) NOTNULL

5. LASTNAME VARCHAR(15) NULL

6. EMAILID VARCHAR(15) NOTNULL

7. SECURITY_QUESTION VARCHAR(15) NOTNULL

8. SECURITY_ANSWER VARCHAR(15) NOTNULL

9. CONTACT_NUM VARCHAR(15) NOTNULL

10 MOBILE_NUM VARCHAR(15) NOTNULL

11 CONTACT_NUM VARCHAR(15) NOTNULL

12 ADDRESS VARCHAR(15) NOTNULL

13 COMPANYNAME VARCHAR(15) NOTNULL COMPANYDETAILS

14 STATUS VARCHAR(15) NOTNULL


(SIZE)

CONSTRAINTS

(KEY)

REFERENCES

FROM

1 JOB_ID INT(10) PRIMARY KEY

2

JOB_CODE VARCHAR(15) NOTNULL

3. JOB_NAME VARCHAR(15) NOTNULL

7/28/2019 prjrpt

25/27

Emp resume details:

Company details:

SNO COLUMN NAME DATE TYPE(SIZE)

CONSTRAINTS(KEY)

REFERENCESFROM

1 COMPANY_ID INT(10) PRIMARYKEY

2 COMPANY_NAME VARCHAR(15) NOTNULL

3 COMPANY_WEBSITE VARCHAR(15) NOTNULL

4 COMPANY_EMAILID VARCHAR(15) NOTNULL

5 COMPANY_INFO VARCHAR(15) NOTNULL

4. JOB_DESCRIPTION VARCHAR(15) NOTNULL

5. POSTED_DATE DATE(12) NOTNULL

6. INTERVIEW_DATE DATE(12) NOTNULL

7. FUNCTIONAL_AREA VARCHAR(15) NOTNULL

8. KEY-SKILLS VARCHAR(15) NOTNULL

9. COMPANY_NAME VARCHAR(15) NOTNULL COMPANY

DETAILS

10 EXPERIENCE INT(4) NOTNULL

11 EMAIL-ID VARCHAR(15) NOTNULL



(SIZE)

CONSTRAINTS

(KEY)

REFERENCES

FROM

1 EMPLOYER_ID INT(10)

FOREIGN KEY EMPLOYER

TABLE

2 SEEKER_ID INT(10) FOREIGN KEY JOB SEEKER

TABLE

7/28/2019 prjrpt

26/27

6 COMPANY_ADDRESS VARCHAR(15) NOTNULL

7 COMPANY_CONTACT INT(10) NOTNULL

Job Fair Details:

SNO COLUMN NAME DATE TYPE(SIZE)

CONSTRAINTS(KEY)

REFERENCESFROM

1 INTERVIEWDATE DATETIME(12) NOTNULL


3FUNCTIONAL_AREA VARCHAR(15) NOTNULL


(SIZE)

CONSTRAINTS

(KEY)

REFERENCES

FROM

7/28/2019 prjrpt

27/27

Seeker_post_resume Details:

1 FIRSTNAME VARCHAR(15) NOTNULL

2 LASTNAME VARCHAR(15) NULL

3 EMAILID VARCHAR(15) NOTNULL


5 SECURITY_ANSWER VARCHAR(15) NOTNULL

6 COUNTRY VARCHAR(15) NOTNULL

7 PHONR_NUM INT(10) NOTNULL

8 MOBILE_NUM INT(10) NOTNULL

9 EXPERIENCE INT(10) NOTNULL

10 ANNNUAL_SALARY INT(10) NOTNULL

11 FUNCTIONAL_AREA VARCHAR(15) NOTNULL

12 COMPANY_NAME VARCHAR(15) NOTNULL

13 SEEKER_ID VARCHAR(15) NOTNULL JOBSEEKER

14 KEY_SKILLS VARCHAR(15) NOTNULL JOBSEEKER

15 RESUME_PATH VARCHAR(15) NOTNULL

16 RESUME-HEADLINE VARCHAR(15) NOTNULL

17 BASIC_QUALIFICATION VARCHAR(15) NOTNULL

prjrpt

Documents