A Project Report on

Job_Portal
MINOR PROJECT SUBMITTED FOR THE DEGREE OF
M.C.A. (MASTER OF COMPUTER APPLICATION)
MCA III YEAR (V SEMESTER)
SESSION: 2009-12

PROJECT GUIDE

SUBMITTED BY:

CERTIFICATE

This is to certify that students Amit Jaiswal, Atul Jaiswal, Kalindi Sharma And Swati
Sharma of MCA (Master of Computer Application) of have completed the project work on
Job Portal within the allotted time.
The software is working perfectly and the work done by them is appreciable. We
find the quality of work presented according to our level of satisfaction. We wish them every
success in life.

Date:
(Project Guide)
Prof: Preeti Gupta

Internal Examinar
Examinar

External

CANDIDATE DECLARATION

I hereby declare that the work which is being presented in this project entitled
Job_Portal in partial fulfillment of degree of Bachelor of Engineering in Computer Science
& Engineering is an authentic record of my own work carried out under the supervision and
guidance of Ms.Preeti Gupta in Department of Computer Science & Engineering, Sanghvi
Institute of Management & science Indore, Rajiv Gandhi Proudyogiki Vishwavidyalaya,
Bhopal.
We are fully responsible for the matter embodied in this project in case of any
discrepancy found in the project and the project has not been submitted for the award of any
other degree.

Date:
Place:

ACKOWLEDGEMENT
We acknowledge our sincere thanks to those who have contributed significantly to this project.
It is a pleasure to extend deep gratitude to our internal guide Mr. Vivek Uprit & Project Guide
(Name) & also our Ms.Preeti Gupta, for this valuable guidance and support and to
continuously prompt us for the progress of the project. We thank him for his valuable
suggestions towards our project, which helped us in making this project more efficient and user
friendly.

We thanks and acknowledge each and every ones efforts that helped us in some or the other
way for small and significant things.

ABSTRACT
Job Portal is a website for job seekers and companys who want to register their job and post
their vacancies. The job seekers who is searching for job can enter, they can register and attach
their resume .Its unique methodology helps in acquiring the client (the person who gives
information about vacancies) and candidate (the person who search for job) information and
segregating them according to the job requirements and vacancies and so the companies also
have to register them so that they can post job and search employee.

The website includes the main feature are as follows:

1) Different companies can register on the website.

2) After registration they can login on the website.
3) The company member can edit their profile and insert, update and delete their personal
info on the website.
4 Companies have to give the info of job requirements and other details.
5) The user can visit the website anytime.
6) The user can do registration on the website after that he/she can able to login on the
website.
7) User can search the job by different categories like according to salary, location, post and
so on.
8) User can communicate with registered companies by sending e-mail through this website.

CONTENT
8

Introduction
1.
2.

.9-12

Analysis
Requirement Analysis

2.2

Use-case Analysis

10.

Activity Diagram

11.

2.3
3.

5.

12.
13-18

Data Model

13.

3.1.1 Dataflow Diagram

17.

3.1.2 Snap shot of HRM

18.

Implementation

31.

5.1

Hardware Specification

31.

5.2

Additional Hardware Components Used

31.

5.3

Platform

31.

5.4

Programming Languages Used

31.
32-37

Testing
6.1

6.

E-R Diagram

Design
3.1

4.

.9

2.1

Conclusion

Test cases and Test Results

32.
37

INTRODUCTION

INTRODUCTION
Job Portal is a website for job seekers and companys who want to register their job and post
their vacancies. The job seekers who is searching for job can enter, they can register and attach
their resume .Its unique methodology helps in acquiring the client (the person who gives
information about vacancies) and candidate (the person who search for job) information and
segregating them according to the job requirements and vacancies and so the companies also
have to register them so that they can post job and search employee.

The website includes the main feature are as follows:

2) Different companies can register on the website.

2) After registration they can login on the website.
3) The company member can edit their profile and insert, update and delete their personal
info on the website.
4 Companies have to give the info of job requirements and other details.
5) The user can visit the website anytime.
6) The user can do registration on the website after that he/she can able to login on the
website.
7) User can search the job by different categories like according to salary, location, post and
so on.
8) User can communicate with registered companies by sending e-mail through this website

2) Analysis:
2.1) REQUIREMENT ANALYSIS-In this we are dealing with the requirement of the proposed system, that is, the
capabilities that the system, which is yet to be developed, should have. It is the
systematic use of proven principles, techniques, languages & tools for the cost
effective analysis, documentation, & on-going evolution of user needs & the
specification of the external behavior of the system to satisfy those user needs. It
provides us a representation of information, function, & behavioral domains that
will be treated by software.
System requirement analysis is a condition of capability needed by us to
solve a problem or achieve an objective. That is, a condition or capability that
must be met or possessed by a system to satisfy a contract, standard specification,
or other formally imposed document.

2.2 Hardware Requirement

2.3 Software Requirement
2.2 Hardware Requirement
2.2.1 Minimum Hardware Requirement

Pentium 3 or higher
30 GB Hard Disk
512 MB RAM or Higher
Monitor
Mouse
Keyboard

2.3 Software Requirement

2.3.1 Minimum Software Requirement

My Eclipse java Enterprice

OS Windows XP or Higher
SQL Server 2005
Tomcate S/w installed

FEASIBILITY ANALYSIS-

3.1 Economic Feasibility

3.2 Technical Feasibility
3.3 Behavioral Feasibility
3.4 Time Feasibility

Activity Diagram:

user

Home page

user

Admin user

Candidate reg.
Project info

New project Entry

Candidate profile

job info

Employer info.

EMP profile

Manage EMP
Text Entry

Manage text info

Sign out

ER-Diagram:

add

name

name

Mob.

id

add

id

Com.nam

user

Manage

ADMIN

mn

mn

EMPLOYER

id
dsgn

name

add

Mob.

Cmp n

DESIGN

3)

Design

There are many aspects to consider in the design of a piece of software. The importance of each
should reflect the goals the software is trying to achieve. Some of these aspects are:

Compatibility - The software is able to operate with other products that are designed for
interoperability with another product. For example, a piece of software may be
backward-compatible with an older version of itself.

Extensibility - New capabilities can be added to the software without major changes to
the underlying architecture.

Fault-tolerance - The software is resistant to and able to recover from component failure.

Maintainability - The software can be restored to a specified condition within a specified

period of time. For example, antivirus software may include the ability to periodically
receive virus definition updates in order to maintain the software's effectiveness.

Modularity - the resulting software comprises well defined, independent components.

That leads to better maintainability. The components could be then implemented and
tested in isolation before being integrated to form a desired software system. This allows
division of work in a software development project.

Packaging - Printed material such as the box and manuals should match the style
designated for the target market and should enhance usability. All compatibility
information should be visible on the outside of the package. All components required for
use should be included in the package or specified as a requirement on the outside of the
package.

Reliability - The software is able to perform a required function under stated conditions
for a specified period of time.

Reusability - the modular components designed should capture the essence of the
functionality expected out of them and no more or less. This single-minded purpose
renders the components reusable wherever there are similar needs in other designs.

Robustness - The software is able to operate under stress or tolerate unpredictable or

invalid input. For example, it can be designed with resilience to low memory conditions.

Security - The software is able to withstand hostile acts and influences.

Usability - The software user interface must be intuitive (and often aesthetically
pleasing) to its target user/audience. In many cases, online help should be included and
also carefully designed.

E-R Modeling

Entity-Relationship model (ER) introduced in 1976 by Peter Chen

Extended ER model (EER) expanded the original ER with new concepts.

Entity

An Entity is a conceptual object

Physically or conceptually exists

Usually a noun in requirement specification e.g. Lecturer, Course, Movie etc.

Entity

Attributes

Multi valued Attribute

Weak Entity

Relationship

Weak Relation

3.1) DFD Diagram of user

DFD Diagram in level 0

User

Login

View
detail

employer

DFD Diagram in level-1

Admin user:
DFD-Diagram Level-1
Admin

Admin user
Login table
Login

View Info.

View table

Entry

Entry Table

Manage HR

Emp. table

DFD Diagram in level 1

User:

DFD Diagram Level-1

H-R User
User
Login table
Login

Company

Company table

Employee

Emp. table

Manage Emp.

Emp. table

Form Designing

Common Home:-

Contact Us:

User Login

User Home:-

For Searching:-

For Search By Category:-

Job Recommendation:-

Maintaining Profile:-

Logout:-

Employer Home:-

Maintain Employer Profile:-

Job Registration:-

Email:-

User Registration Table :-

User login Tabel:-

Company Info Table:-

Company Type Table:-

Company Login Table:-

Job Info Table:-

State Table:-

City Table:-

4) Implimentation:
4.1 Hardware Requirement
4.1.1 Minimum Hardware Requirement

Pentium 3 or higher
30 GB Hard Disk
512 MB RAM or Higher
Monitor
Mouse
Keyboard

4.2 Software Requirement

4.2.2 Minimum Software Requirement

OS Windows XP or Higher
SQL Server 2005

4.3)Platform:

Window xp,window 7
4.4)Programing Language Used:

Dot Net

5) TESTING
5.1) Testing
Software testing is any activity aimed at evaluating an attribute or capability of a
program or system and determines that it meets its required results. Although crucial to software
quality and widely deployed by programmers and tester, software testing still remains an art,
due to limited understanding pf the principle of software. The difficulty in software testing
stems from the complexity of software: we cannot completely test a program with moderate
complexity. Testing is more than just debugging. The purpose of testing can be quality
assurance, verification and validation or reliability estimation. Testing can be used as a generic
metrics as well. Correctness testing and reliability testing are two major areas of testing. In
general, software testing is the process of executing a program or system with the intent of

finding errors. Or, it involves any activity aimed at evaluating an attribute or capability of a
program or system and determining that it meets its required result. Software bugs will almost
always exist in any software module with moderate size, because the complexity of software is
generally intractable. Testing is an integral part in software development. It is broadly deployed
in every phase in the software development cycle. Typically, more than 50% percent of the
development time is spent in testing.

5.2)Testing principles
To guide software testing there are few principles:
1. All tests should be traceable to customer requirements. It follows that the more severe
defects are those that cause the program to fail to meet its requirements. So here we test
the functional requirements of the system to meet the original requirements.
2. Tests should be planned long before testing begins. Test planning can begin as soon as
the requirements model is complete. Detailed definition of test cases can begin as soon
as the design model has been solidified. Therefore, all test cases can be planned and
designed before any code has been generated.
3. The Pareto principle applies to software testing. The Pareto principle implies that 80
percent of all uncovered errors during testing will likely be traceable to 20 percent of all
program modules. The problem, of course, is to isolate these suspect modules and to
thoroughly test them.
4. Testing should begin in the small and progress towards testing in the large. The first
planned and executed generally focus on individual program modules. As testing
progresses, testing shift focus in an attempt to find errors in integrated clusters of
modules and ultimately in the entire system.
5. Exhaustive testing is not possible. The number of path permutations for even a
moderately sized program is exceptionally large. For this reason, it is impossible to
execute every combination of paths during testing. This is possible, however, to
adequately cover program logic and to ensure that all conditions in the procedural
design have been exercised.

6. To be most effective, an independent third party should conduct testing. The meaning of
most effective testing is that one has the highest probability of finding errors.
Testing is usually performed for the following purposes:
To improve quality:
Quality means the conformance to the specified design requirement. Being correct the
minimum requirement of quality, means performing as required under specified circumstances.
Debugging a narrow view of software testing is performed heavily to find out design defects by
the programmer.
For reliability estimation
Software reliability has relation with many aspects of software, including the
structure and the amount of testing it has been subjected to.
The testing process involves the following steps:
i.

Plan for testing

ii.

Identifying applicable types of testing

iii.

Defining and configuring the test environment

iv.

Test case creation and execution

v.

Bug fix, defects analysis and casual analysis

Initially the test strategy is defined, in which the type is decided and the level of testing would
be done in the project.

5.3 Testing Stages

There are four main testing stages:
i.

Unit testing

ii.

Integration testing

iii.

System testing

iv.

User testing

(A) Unit Testing

This test demonstrates that a single program, module or unit of code function as
designed. The unit testing is normally white box oriented, and the step can be calculated in
parallel for multiple modules.

(B) Integration Testing

This test is done to validate the multiple parts of the system interact according to the
system design. Each integrated portion of the system is ready for testing with other parts of the
system. The objectives are to take unit tested modules and built a program structure that has
been dictated by design.

(C)System Testing
This test simulates operation of the entire system and confirms that it runs correctly the
total system is also tested for recovery and back after various major failures to ensure that no
data is lost during the emergency.

(D) User Acceptance Testing

Internal staff, customer, vendor or other user interacts with the system to ensure that it
will function as desired regardless of the system requirement. An acceptance test has the
objectives of selling the user on the validity and reliability of the system. It verifies that the
systems procedure operates to system specification and the integrity of vital data is maintained.
Some more testing:
i.

Performance testing

ii.

Load testing

iii.

Stress testing

iv.

Security and access control testing

v.

Regression testing

(E) Performance Testing

The goal of performance testing is to verify performance requirement have been achieved.

(F) Load Testing

This testing verifies the ability of the system to continue to function properly under different
workloads.

(G) Security Testing

System level security that only those actors granted access to the system is capable of accessing
the application and through the appropriate gateways

(H) Black-box testing

The black-box approach is a testing method in which test data are derived from the specified
functional requirements without regard to the final program structure. It is also termed datadriven, input/output driven or requirements-based testing. Because only the functionality of the
software module is of concern, black-box testing also mainly refers to functional testing -- a
testing method emphasized on executing the functions and examination of their input and
output data. The tester treats the software under test as a black box -- only the inputs, outputs
and specification are visible, and the functionality is determined by observing the outputs to
corresponding inputs. In testing, various inputs are exercised and the outputs are compared
against specification to validate the correctness. All test cases are derived from the specification.
No implementation details of the code are considered.
It is obvious that the more we have covered in the input space, the more problems we will find
and therefore we will be more confident about the quality of the software. Ideally we would be
tempted to exhaustively test the input space. But as stated above, exhaustively testing the
combinations of valid inputs will be impossible for most of the programs, let alone considering
invalid inputs, timing, sequence, and resource variables. Combinatorial explosion is the major
roadblock in functional testing. To make things worse, we can never be sure whether the
specification is either correct or complete. Due to limitations of the language used in the
specifications (usually natural language), ambiguity is often inevitable. Even if we use some
type of formal or restricted language, we may still fail to write down all the possible cases in the
specification. Sometimes, the specification itself becomes an intractable problem: it is not
possible to specify precisely every situation that can be encountered using limited words. And
people can seldom specify clearly what they want -- they usually can tell whether a prototype is,
or is not, what they want after they have been finished. A specification problem contributes
approximately 30 percent of all bugs in software.
The research in black-box testing mainly focuses on how to maximize the effectiveness of
testing with minimum cost, usually the number of test cases. It is not possible to exhaust the
input space, but it is possible to exhaustively test a subset of the input space. Partitioning is one
of the common techniques. If we have partitioned the input space and assume all the input
values in a partition is equivalent, then we only need to test one representative value in each

partition to sufficiently cover the whole input space. Domain testing partitions the input domain
into regions, and considers the input values in each domain an equivalent class. Domains can be
exhaustively tested and covered by selecting a representative value(s) in each domain.
Boundary values are of special interest. Experience shows that test cases that explore boundary
conditions have a higher payoff than test cases that do not. Boundary value analysis requires
one or more boundary values selected as representative test cases. The difficulties with domain
testing are that incorrect domain definitions in the specification can not be efficiently
discovered.

6) Conclusion:
From a proper analysis of positive points and constraints on the
component, it can be safely concluded that the product is a highly
efficient GUI based component. This component can be easily
plugged in many other systems.
Also the component is user friendly. Generally the TPOs of the
Colleges has to face a lot of problems in management of the
Students information. This all information has to be managed
manually. So, there is a need to develop a system that can solve the
mentioned problem. This software comes with just that solution.

Bibliography & References

Reference Books:1. Asp.net Complete Reference
2. Asp.net e book
3. Software Engineering Roger S. Pressman
4. Database system concepts Henry F.Korth