8.

Cost estimation of
project

Today, software is the most expensive element of virtually all computer-

based systems. For complex, custom systems, a large cost estimation

error can make the difference between profit and loss. Cost overrun cab

be disastrous for the developer. Software cost and effort estimation will

never be an exact science. Too many variables – human, technical,

environment, political – can affect the ultimate cost of software and

effort applied to develop it. Estimating the cost of a project is indeed a

very important task which one needs to achieve while developing a

project. The Cost Estimation Of A Project takes into account the

following factors :

Overhead Cost The Overhead Cost includes cost of research, books,

internet time, etc. The development of any software project does require

some research work. The person In charge of the project may have to

consult and buy books. He may also have to surf the net for tips and

suggestions.

Cost of the Development Software

This includes any extra cost which may be incurred in the development

of the software.

Cost of the Development Time

No. of Man-hours worked * hourly rate

It is the no. of hours the developer(s) will work to develop the software

multiplied by an hourly rate as decided mutually by the client and the

developer.

Peripheral Cost

Peripheral Cost includes cost of stationery and peripherals like hubs ,

cables etc. required for the development of the software.

Calculation of Project Cost

Total Project Development Time:

No. of days required for completion of the project = 95 days.

Personnel Working on the Project = 1 No.

Working Hours per day = 6 hrs.

Total Man-hours = 95 x 6 = 570

Hourly Rate = Rs. 15.00

Total Man-hour Cost = 570 x 15

= Rs. 8,550.00

Peripheral Cost = Rs. 1,500.00

Overhead Cost = Rs. 1,000.00

Total Cost of the Project = Rs. 11,050.00

 9.Report

There are two types of reports that are extremely useful for the users who searches
for jobs
1) Alljobs.jsp - this module dislays all the available jobs that are currently
posted by the employers. The job searchers can see all the jobs posted and
select whichever suites them and apply to it immediately. This reports shows
all the description of jobs , the location, experience and the qualifications
required. So this report is very user friendly for the job searchers.
2) Jobsearchresults.jsp – This is another extremely useful report for the job
searchers. Here the jobs can be searched by different options like
a)Experience –the user puts the experience in a text box and
all the jobs matching that will be displayed.
b) Location –the user puts the Location in a text box and all the
jobs matching that will be displayed.
 c)Qualification –the user puts the Qualification in a text box and
all the jobs matching that will be displayed.
Also the user can select all the criteria at the same time and all the
jobs matching all the criteria’s will be displayed.
So this report is another extremely useful report for the job searchers.

10.PERT And
GNATT chart
PERT / CPM consists of two basic elements, activities and event. The

chart clearly shows the sequence an interrelationships of activities in the

project. To represent dependencies, PERT chart is often used. A PERT

chart is a graph based chart. It can be used to determine the activities

that form the “Critical Path”, which if delayed will caused the over all

project to delayed. PERT stands for Program Evaluation Review

Technique, a methodology developed by the U.S. Navy in the 1950s to

manage the Polaris submarine missile program. A similar methodology,

the Critical Path Method (CPM), which was developed for project

management in the private sector at about the same time, has become

synonymous with PERT, so that the technique is known by any

variation on the names: PERT, CPM, or PERT/CPM. Program

evaluation and review technique (PERT) charts depict task, duration,

and dependency information. Each chart starts with an initiation node

from which the first task, or tasks, originates. If multiple tasks begin at

the same time, they are all started from the node or branch, or fork out

from the starting point. Each task is represented by a line which states

its name or other identifier, its duration, the number of people assigned

to it, and in some cases the initials of the personnel assigned. The other

end of the task line is terminated by another node which identifies the

start of another task, or the beginning of any slack time, that is, waiting

time between tasks. PERT charts are usually drawn on ruled paper with

the horizontal axis indicating time period divisions in days, weeks,

months, and so on. Although it is possible to draw a PERT chart for an

entire project, the usual practice is to break the plans into smaller, more

meaningful parts. This is very helpful if the chart has to be redrawn for

any reason, such as skipped or incorrectly estimated tasks. Many PERT

charts terminate at the major review points, such as at the end of the

analysis. Many organizations include funding reviews in the projects

life cycle. Where this is the case, each chart terminates in the funding

review node. A PERT chart presents a graphic illustration of a project as

a network diagram consisting of numbered nodes (either circles or

rectangles) representing events, or milestones in the project linked by

labelled vectors (directional lines) representing tasks in the project. The

direction of the arrows on the lines indicates the sequence of tasks. In

the diagram, for example, the tasks between nodes 1, 2, 4, 8, and 10

must be completed in sequence. These are called dependent or serial

tasks. The tasks between nodes 1 and 2, and nodes 1 and 3 are not

dependent on the completion of one to start the other and can be

undertaken simultaneously. These tasks are called parallel or

concurrent tasks. Tasks that must be completed in sequence but that

don't require resources or completion time are considered to have event

dependency. These are represented by dotted lines with arrows and are

called dummy activities. For example, the dashed arrow linking nodes 6

and 9 indicates that the system files must be converted before the user

test can take place, but that the resources and time required to prepare

for the user test (writing the user manual and user training) are on

another path. Numbers on the opposite sides of the vectors indicate the

time allotted for the task.

 TASKS TIME NEEDED

A) SYSTEM STUDY 12 DAYS

B) INFORMATION GATHERING 12 DAYS

C) FEASIBILITY STUDY 5 DAYS

D) DATABASE DESIGN 7 DAYS

E) FORM DESIGN 10 DAYS

F) CODING 30 DAYS
 G) TESTING WITH SAMPLE DATA 15 DAYS

H) USER / OPERATIONAL MANUAL 2 DAYS

PERT CHART
29
 1 A 2 B 3 C 4

12 12 5

0 12 24 D

5
31

10 E

H G F

9 8 7 6
2 15 30

88 86 71 41

Total 88 days

Critical Path: A B D E F G H
 Directional arrows represent dependent tasks that must be

completed

sequentially.

Numbered Circles are nodes and represent events.

The numbers on the arrows represent the time taken to complete the

tasks. Show

within ( ).

GANTT CHART:-

A conceptually simple and effective scheduling technique is the Gantt

Chart, which uses a calendar oriented chart to represent the project

schedule. Each activity is represented as a bar in the calendar, starring

from the starting date of the activity and ending at the ending date for

that activity. The start and end of each activity become milestones for

the project. Progress can be represented easily in a Gantt chart, by

ticking off each milestones is completed. Alternatively, for each activity

another bar can be drawn specifying when the activity actually started

and ended. A Gantt chart is a matrix which lists on the vertical axis all

the tasks to be performed. Each row contains a single task identification

which usually consists of a number and name. The horizontal axis is

headed by columns indicating estimated task duration, skill level needed

 to perform the task, and the name of the person assigned to the task,

followed by one column for each period in the project's duration. Each

period may be expressed in hours, days, weeks, months, and other time

units. In some cases it may be necessary to label the period columns as

period 1, period 2, and so on. The main drawback of the Gantt chart is

that it does not depicted the dependency relationships among the

different activities.

12 12 DAYS 5 DAYS 7 DAYS 10 30 15 DAYS 2 DAYS

DAYS DAYS DAYS

SYSTE INFORMATIO FEASIBILIT DATABASE FORM CODIN TESTIN USER /

M N GATHERING Y STUDY DESIGN DESIG G G WITH OPERATIONA

STUDY N SAMPLE L MANUAL

DATA

GNATT CHART of On Line Job Search

11.Future scope and further
enhancement of project
There always remains a scope for further improvement and further addition of features to

an already existing application. In software development it is always kept in mind

moreover that the existing applications do prove to be beneficial for future uses too.

Applications are always devised keeping in mind its future implications.

We have plan for future addition that we can send sms alert from our site and we will also

have payment processing system in our site.

12. Bibliography
To build the project we have collected information from following
sources:

(1) www.google.co.in
(2) Java Server Page(O’Relly Publication)
(3) Web Technologies-(Godbole,Kahate)
(4) Web Technology & Design-(Xavier)