CHAPTER 4

Effort Estimation and Scheduling

Presented ByRahul Chiplunkar - 015 Rucha Pimplikar - 072

Charu Nayyar 118

Effort Estimation
Estimation for Effort (How many resources required?) Schedule (What is the timeline?) Estimating - The process of forecasting or approximating the time and cost of completing project deliverables Effort Estimation Done at an early stage of the project Can rely on a hunch or previous experience Size is a critical factor in determining Effort Schedule Cost The secret to good estimates is the clear understanding of the tasks Poor size estimation is one of the main reasons major software projects ultimately fail

Measuring Size of a Project

Size measures include source lines-of-code (SLOC) function points feature points Complexity is a function of size Complexity must be continuously measured, tracked and controlled

Basic Steps in Software Estimation

Identify project objectives and requirements Plan the activities Estimate product size and complexity Estimate effort, cost and resources Develop projected schedule Compare and iterate estimates Follow up

Types of Estimates
Top-down (macro) estimates  Size estimate is used to determine estimate for overall effort  Effort for various phases/activities is then determined as a percentage of the total effort Bottom-up (micro) estimates  Estimate obtained first for parts of the project  Overall estimate then derived from the estimates of its parts  This approach is a judicious mix of experience and data

Estimating a Schedule
Once effort is known or fixed, various schedules are possible ExampleA project with an effort estimate of 56 personmonths can have Schedule of 8 months with 7 people OR Schedule of 7 months with 8 people Manpower & months are NOT fully interchangeable in a software project

The Bottom-up Estimation Approach

Task unit approach Software under development divided into major programs (units) Each program (unit) then classified as Simple, Medium or Complex (S/M/C) Standard effort for coding & self testing (build effort) is determined Project specific factors are used to refine the build effort Total build effort is then calculated Using the effort distribution given in the capability baseline or for similar projects given in the process database, effort for other tasks is estimated to thus get the total effort

TOP DOWN APPROACH

 Size
 

of Software

Why it is important? Measuring Size

Project Estimate Times Costs

Macro (Topdown)Approaches
SLOC Consensus methods Ratio methods Apportion method Function point methods for software and system projects Learning curves

TOP DOWN APPROACH

Total size is calculated by function point analysis. Productivity data taken from process capability baseline is fixed for new similar project. Overall effort is estimated. Use effort distribution data from PCB. Refine the estimates.

FUNCTION POINT ANALYSIS METHOD(FPA)

 Function

point count is based on users perspective of functions expected to be delivered. the functions delivered by the product from technology platform on which product is developed.

 Separates

EXAMPLE :-

INPUTS TO SIZING
SLOC - Traditional FP Object points Feature points similar to Function points.

USE CASE POINTS APPORACH

The Use Case Points Estimation Method was introduced by Gustav Karner from Linkping University. Can be applied if use cases are used for requirement specification. The method is inspired by the Function Point (FP) method.

DETAIL - USE CASE POINTS APPORACH

The Use Cases are categorized depending on the number of transactions as
Categories Simple Average Complex Transactions 3 or less 4 to 7 7 or more Weight age 5 10 15

The unadjusted Use Case points(UUCP) are calculated by product of no. of use cases of particular complexity and factor for that complexity and then adding all the weighted actors and Use Cases. Adjusting the raw UUCP according to the TCF (Technical Complexity Factor)

TECHNICAL COMPLEXITY FACTOR

Factor number T1 T2 Factor description Distributed system Response or throughput performance objective End-user efficiency Complex internal processing Code must be reusable Easy to install Easy to use Portable Easy to change Concurrent Includes special security features Provides direct access for third parties Special user training facilities are required Weight 2 1

T3 T4 T5 T6 T7 T8 T9 T10 T11 T12 T13

1 1 1 0.5 0.5 2 1 1 1 1 1

Each factor is assigned a value from 0 to 5 based on importance and how it is supported by the technology used.

ENVIRONMENTAL FACTOR
F tor nu b r F tor d ription ight

F1 F2 F3 F4 F5 F6 F7 F8

Familiar wit v lopmet met od Application experience O ect-oriented experience Lead analyst capability Motivation table requirements art-time workers xperience wit t e tools

1. . 1 . 1 2 -1 -1

Each factor is assigned a value from 0 to 5

SCHEDULING
How to make schedule ? Can we change schedule after making it ? Which method is used for scheduling ?

OVERALL SCHEDULING
Meaning Method used for overall scheduling Thumb rule used by Project managers Determining Milestones

ACTUAL v/s ESTIMATE SCHEDULE

DETAILED SCHEDULING
Meaning How we can do it ? Continuous Review