Download - Job Portal

Transcript
Page 1: Job Portal

A

Practical Training Seminar Report

On

“Job Portal”

Submitted in partial fulfillment

of requirement for Degree 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

Page 2: Job Portal

A

Practical Training Seminar Report

On

“Job Portal”

Submitted in partial fulfillment

of requirement for Degree 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

Page 3: Job Portal

Suresh Gyan Vihar University

Mahal Jagatpura,Jaipur

Certificate of Practical Training Seminar Report 2012-13

It is here to certify that Anita, Aarif Habib, student of Master Of Computer Application II year (4th SEM) 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 Master Of Computer Application. Examination.

Gajanand Sharma

PTS In charge Assistant Professor CSE Department

Page 4: Job Portal

INDEX

1. ABOUT THE TECHNOLOGY 1

1.1. ASP .NET INCLUDES 1

1.2. ASP FILE 2

1.3. .NET FRAMEWORK 2

1.4. DIFFERENCE BETWEEN ASP AND ASP.NET 2

1.5. NEW IN ASP.NET 3

1.6. ASP.NET CONTROLS 3

1.7. ASP.NET SERVER CONTROLS 3

1.8. HTML SERVER CONTROLS 3

1.9. ASP.NET WEB SERVER CONTROLS 3

1.10. ASP.NET VALIDATION SERVER CONTROLS 4

2. LITERATURE SURVEY 5

2.1. STUDY OF EXISTING SYSTEM 52.2. STUDY OF IMPLEMENTED SYSTEM 5

3. PROBLEM STATEMENT 10

4. PROBLEM ANALYSIS 10

4.1. PLANNING 10

4.2. PROJECT REQUIRMENTS 11

4.3. REQUIREMENT ANALYSIS 11

4.4. FEASIBILITY ANALYSIS 12

5. PROBLEM DESIGN 14

5.1. HIGH LEVEL DESIGN 14

6. DATA DICTIONARY 26

Page 5: Job Portal

1. ABOUT THE TECHNOLOGY

1.1 ASP.NET

ASP.net is the latest version of Microsoft’s Active Server pages Technology (ASP).

ASP.NET is a unified Web development model that includes the services necessary for you

to build enterprise class web application with a minimum of coding. ASP.net is part of .net

framework, and when coding ASP.net you have access to classes in the .net framework. You

can code your applications in any language compatible with the common language runtime

(CLR), including Microsoft Visual Basic, C#, and Jscript, .Net and J #. These languages

enable you to develop ASP.Net applications that benefit from the common language runtime,

type safety and inheritance and so on.

1.1.1 ASP.NET Includes

A page and control framework.

The ASP.NET compiler.

Security Infrastructure.

State-management facilities.

Application configuration.

Health monitoring and performance features.

Debugging support.

An XML web service framework.

Extensible hosting environment and application life cycle management.

An extensible designer environment.

ASP is a server side scripting technology that enables scripts (embedded in web pages)

to be executed by an Internet Server.

ASP is a Microsoft technology.

ASP stands for Active Server Pages.

ASP is a program that runs inside IIS.

IIS stands for Internet Information Services.

IIS is a free component with Windows 2000.

IIS is also a part of the Windows NT 4.0 Option pack.

Page 6: Job Portal

PWS is a smaller – but fully functional version of IIS.

PWS can be found on your windows 95/98 CD.

1.1.2 ASP FILE

An ASP file is just the same as an HTML file.

An ASP file can contain text, HTML, XML and scripts.

Scripts in an ASP file are executed on the server.

An ASP file has the file extension “.asp”.

1.1.3 NET FRAMEWORK

The .NET framework is the infrastructure for the Microsoft .NET platform.

The .NET Framework is an environment for building, deploying and running

web applications and the .NET framework contains a common language runtime

and common class libraries like ADO.NET, ASP.NET and Windows Forms – to

provide advanced standard services that can be integrated into a variety of

computer systems.

The.NET framework provides a feature-rich application environment,

simplified development and easy integration between a numbers of different

development languages.

The .NET framework is language neutral. Currently it supports C++, C#,

Visual Basic and Jscript. Microsoft Visual Studio.Net is a common development

for the .net framework.

1.1.4 Differences between ASP and ASP.NET

ASP .NET has a better language support, a large set of new controls and XML

based components and better user authentication.

ASP.NET provides increased performance by running compiled code.

ASP.NET is not fully backward compatible with ASP.

Page 7: Job Portal

1.1.5 New in ASP.NET

Better language support, Programmable controls.

Event –Driven programming, XML-Based components.

User authentication, with accounts and roles.

Higher scalability, Increased performance.

Easier configuration and deployment.

Not fully ASP compatible.

1.1.6 ASP.NET Controls

ASP.NET contains a large set of HTML controls. Almost all HTML

controls on a page can be defined as ASP.NET control objects that can be

controlled by scripts .ASP.NET also contains a new set of object oriented input

controls , like programmable list boxes and validation controls. A new data grid

control supports sorting, data paging and everything you expect from a dataset

1.1.7 ASP.NET - Server Controls

Server controls are components that are executed on the server

Each server control is an instance of a particular class with methods,

properties and events associated with it

There are three kinds of server controls

HTML Server Controls - Traditional HTML tags

Web Server Controls - New ASP.NET tag

Validation Server Controls - For input validation

1.1.8 HTML Server Controls

HTML elements in ASP.NET files are, by default, treated as text

To make these elements programmable, add a runat=" server" attribute to them.

It indicates that element should be treated as a server control.

All HTML server controls must be within a <form> tag.

May have events, methods, and properties attached to them

1.1.9 ASP.NET - Web Server Controls

Web server controls are traditional form controls like BUTTON, CHECK

BOX, TEXT BOX, etc.

Page 8: Job Portal

Web server controls are special ASP.NET tags understood by the server

They require a runat="server" attribute to work. The syntax for creating a Web

server control is:

<asp: control_nameid="some_id" runat="server" />

1.1.10 ASP.NET - Validation Server Controls

Validation server controls are used to validate user-input so that wrong type of data

can’t be filled in database table.

Validation controls are attached to an input control, such as a TextBox for which the

input is to be validated

Syntax:

<asp: control_nameid="some_id" runat="server" />

Page 9: Job Portal

2. LITERATURE SURVEY

2.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.

2.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.

2.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?

Page 10: Job Portal

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?

3. 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.

4. PROBLEM ANALYSIS

4.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.

4.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.

Page 11: Job Portal

4.1.2 PROJECT DELIVERABLES

Website Source

Code A

Project Report

4.1.3 PROJECT SCHEDULE

Planning and requirement analysis phase 5 days Design phase 15 days Coding 20 days Testing 5 days

4.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.

4.3 REQUIREMENT ANALYSIS

4.3.1 FUNCTIONAL REQUIREMENTS

The various features or functional requirements are:

· The administrator can verify registrations of the new users.

Page 12: Job Portal

· 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 after successful logging in to the project.

· The user can also send there billing details.

4.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.

4.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 Feasibility2. Technical Feasibility 3. Operational Feasibility

4.4.1 OPERATIONAL FEASIBILITY

The 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

Page 13: Job Portal

4.4.2 TECHNICAL FEASIBILITY

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

4.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

Page 14: Job Portal

using computers for other purpose, so that there is no additional cost to be incurred for adding this system to its computers. The backend required for storing other details is also the same database that is MySQL. The computers in the organization are highly sophisticated and don’t needs extra components to load the software. Hence the organization can implement the new system without any additional expenditure. Hence, it is economically feasible.

5. PROJECT DESIGN

5.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.

Page 15: Job Portal

DFD

Level 0 Diagram for Jobbing Portcullis :

Level 1 Diagram for Admin:

Level 1 Diagram for Job seeker:

Page 16: Job Portal

Level 1 Diagram for Employer:

Page 17: Job Portal

Level 2 Diagram for Admin:

Page 18: Job Portal
Page 19: Job Portal

Level 2 Diagram for Job seeker:

Level 2 Diagram for Employer:

Page 20: Job Portal
Page 21: Job Portal

ERD

DB DESIGN:

Entities:

1. Admin2. Job fair3. Job details4. Company Details5. Seeker Details6. Post Resume7. 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

Page 22: Job Portal

5.Seeker details:

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

Page 23: Job Portal

Has

Has

Admin Employer

AdminCompany

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

Page 24: Job Portal

SeekerDetails JobDetails Has

Company EmployerHas

JobSeekersEmployersHas

SeekerID

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)

SeekerEmailID

ContactNo.

EmployerID(FK)

Page 25: Job Portal

Data Dictionary:

EmployerID(PK)

Password

FirstName

LastName

EmailID

Location

CompanyID(FK)

Status

Page 26: Job Portal

Admin:

SNO COLUMN NAME DATA TYPE (SIZE)

CONSTRAINTS (KEY)

REFERENCESFROM

1 ADMINID VARCHAR(15) PRIMARY KEY

2PASSWORD VARCHAR(15) NOTNULL

Job Seekers:

SNO

COLUMN NAME DATA TYPE (SIZE)

CONSTRAINTS (KEY)

REFERENCESFROM

1 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

Employer Details:

Page 27: Job Portal

SNO COLUMN NAME DATA TYPE (SIZE)

CONSTRAINTS (KEY)

REFERENCESFROM

1 EMPLOYER_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. 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 COMPANY DETAILS

14 STATUS VARCHAR(15) NOTNULL

Job Details:

SNO COLUMN NAME DATA TYPE (SIZE)

CONSTRAINTS (KEY)

REFERENCESFROM

1 JOB_ID INT(10) PRIMARY KEY

Page 28: Job Portal

2JOB_CODE VARCHAR(15) NOTNULL

3. JOB_NAME 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

12 LOCATION VARCHAR(15) NOTNULL

Emp resume details:

SNO COLUMN NAME DATA TYPE (SIZE)

CONSTRAINTS (KEY)

REFERENCESFROM

1 EMPLOYER_ID INT(10)FOREIGN KEY EMPLOYER

TABLE

2 SEEKER_ID INT(10) FOREIGN KEY JOB SEEKER TABLE

Company details:

SNO COLUMN NAME DATE TYPE(SIZE)

CONSTRAINTS(KEY)

REFERENCES FROM

1 COMPANY_ID INT(10) PRIMARYKEY

Page 29: Job Portal

2 COMPANY_NAME VARCHAR(15) NOTNULL

3 COMPANY_WEBSITE VARCHAR(15) NOTNULL

4 COMPANY_EMAILID VARCHAR(15) NOTNULL

5 COMPANY_INFO VARCHAR(15) NOTNULL

6 COMPANY_ADDRESS VARCHAR(15) NOTNULL

7 COMPANY_CONTACT INT(10) NOTNULL

Job Fair Details:

SNO COLUMN NAME DATE TYPE(SIZE)

CONSTRAINTS(KEY)

REFERENCES FROM

1 INTERVIEWDATE DATETIME(12) NOTNULL

2 LOCATION VARCHAR(15) NOTNULL

3FUNCTIONAL_AREA VARCHAR(15) NOTNULL

Seeker_post_resume Details:

SNO COLUMN NAME DATA TYPE (SIZE)

CONSTRAINTS (KEY)

REFERENCESFROM

1 FIRSTNAME VARCHAR(15) NOTNULL

Page 30: Job Portal

2 LASTNAME VARCHAR(15) NULL

3 EMAILID VARCHAR(15) NOTNULL

4 LOCATION 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


Top Related