Scribd
Upload
60 views10 pages

Software Effort Estimation

This document discusses software effort estimation, which is the process of forecasting how much effort is required to develop or maintain software. It covers why estimation is important, challenges in estimation, using past project data to estimate programmer productivity, and different techniques for software estimation like algorithm models, expert judgement, and analogy.

Uploaded by

Savithri Subramanian
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
60 views10 pages

Software Effort Estimation

This document discusses software effort estimation, which is the process of forecasting how much effort is required to develop or maintain software. It covers why estimation is important, challenges in estimation, using past project data to estimate programmer productivity, and different techniques for software estimation like algorithm models, expert judgement, and analogy.

Uploaded by

Savithri Subramanian
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 10

SOFTWARE EFFORT ESTIMATION

PREPARED BY ,
SAVITHRI S
What is Software Effort Estimation?

 Process of forecasting how much effort is required to develop or maintain a


software application.
 Measured in hours worked by a person or the money needed to pay for this
work.
 Draft project plans and budget in early stages of SDLC.
 Used for accurately predicts cost and allocate resources accordingly.
Why to Estimate?

 On- Time
 Within Budget
 Required Quality

 Then we need target.


 Target should be reasonable and realistic.
Challenges in Software Effort Estimation

 Underestimating Small tasks


 Overestimating large tasks 3
 Political Implications
[Government is conducting TNPSC or any other Exams]

Changing Technology
Programmer Productivity = SLOC/ Day
SLOC Source Lines Of Code
It is all difficult to predict (because people may fallen sick, network connection is poor)
PAST PROJECT DATA

PROJECT DESIGN CODING TESTING TOTAL SLOC


WM WM WM WM
A 3.7 5.3 7.4 16.7 6050
B - - -
C - - - 17.3 3315
D - - - 10.1 38614

FOR PROJECT A: SLOC = 6050 , WM=16.7 NUMBER OF DAYS = 16.7*30 = 501 DAYS
SLOC/DAY = 6050/501 = 12.7 SLOC/ DAY
FOR project C: SLOC= 3315 WM = 17.3 , NO OF DAYS= 17.3 * 30 = 519 SLOC/DAYS =
3315/519 = 6.7 SLOC/DAY
Where are estimates done?

 Strategic Planning  Staff recruitment, Project Portfolio


Management
 Feasibility Study  to confirm the benefit
 System Specification  Estimates of design proposals
 Evaluation of Prooposals  Estimate worthiness
 Project Planning  Confirms at the earlier stage
PROBLEMS WITH OVER ESTIMATES

 PARKINSONS LAW:
 WORK EXPANDS TO FILL THE TIME AVAILABLE.
EASY TARGET – STAFF WORK
 BROOKS LAW : PUTTING MORE PEOPLE ON A LATE
JOB MAKES IT LATER
PROBLEMS WITH UNDER ESTIMATES

 LESS SEVERITY
 THE DANGER IS QUALITY
 MOTIVATION AND MORALE ARE ENHANCED
 UNREALISTIC- MOTIVATION ARE REDUCED
BASIS FOR SOFTWARE ESTIMATION

 THE NEED FOR HISTORICAL DATA


 PARAMETER
 1. EFFORT – WM / PM 2. SURATION
 12 * 1 , 1 * 12, 3 * 4,4 * 3
 TECHNIQUES:
 ALGORITHM MODELS EXPERT JUDGEMENT(ADVICE OF
KNOWLEDGEABLE STAFF)ANALOGY(SIMILAR COMPLETED
PROJECTS)PARKINSON  PRICE TO WIN(LOW ESTIMATE TO WIN
CONTRACT) TOP DOWN(OVERALL ESTIMATE IS BROKEN DOWN) 
BOTTOM UP(ESTIMATE OF TASKS ARE AGGREGATED)
SOFTWARE EFFORT ESTIMATION

You might also like