Scribd
Upload
80 views11 pages

Project Estimation and Decomposition Techniques

Uploaded by

navibbajracharya27
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
80 views11 pages

Project Estimation and Decomposition Techniques

Uploaded by

navibbajracharya27
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/ 11

Project Estimation and

Decomposition Techniques
Project Estimation Techniques
• Estimation of various projects parameters is an important project
planning activity. The different parameters of a project that need to
be estimated include –
• Project Size
• Effort required to complete the project
• Project Duration
• Cost
Decomposition Techniques
• Software project estimation is a form of problem solving, incase is too
complex to be considered in one piece. For this reason, we decompose
the problem, recharacterizing it as a set of smaller (and hopefully, more
manageable) problems.

• The decomposition approach was discussed from two different points


of view: decomposition of the problem and decomposition of the
process. Estimation uses one or both forms of partitioning. But before
an estimate can be made, the project planner must understand the
scope of the software to be built and generate an estimate of its “size.”
1. Software Sizing
• The degree to which the planner has properly estimated the size of
the product to be built.
• The ability to translate the size estimate into human effort, calendar
time, and dollars.
• The degree to which the project plan reflects the abilities of the
software team.
• The stability of product requirements and the environment that
supports the software engineering effort.
Different approaches to the sizing problem:
1. Fuzzy Logic Sizing:
• This approach uses the approximate reasoning techniques.
• The planner must identify the type of application, establish its magnitude on a qualitative scale, and
then refine the magnitude within the original range.
2. Function Point Sizing
• The planner develops estimates of the information domain characteristics
3. Standard Component Sizing
• Software is composed of a number of different “standard components” that are generic to a
particular application area. e.g. Information system are subsystems: modules, screens, reports,
interactive programs, batch programs, files,
4. Change Sizing
• This approach is used when a project encompasses the use of existing software that must be modified
in some way as part of a project.
• The planner estimates the number and type (e.g., reuse, adding code, changing code, deleting code)
2. Problem Based Estimation
• LOC and FP data are used in two ways during software project
estimation:
(1) as an estimation variable to "size" each element of the software and
(2) as baseline metrics collected from past projects and used in
conjunction with estimation variables to develop cost and effort
projections.
3. Process Based Estimation
• Estimating a project is to base the estimate on the process that will be
used.
• The process is decomposed into a relatively small set of tasks and the
effort required to accomplish each task is estimated.
3. Empirical Estimation Models
• Uses empirically derived formulas to predict effort as a function of
LOC or FP.
1. The Structure of Estimation Models
E = A + B x (ev)C
where A, B, and C are empirically derived constants,
E is effort in person-months, and
ev is the estimation variable (either LOC or FP).
• LOC-oriented estimation models:
E = 5.2 x (KLOC)0.91 Walston-Felix model
E = 5.5 + 0.73 x (KLOC)1.16 Bailey-Basili model
E = 3.2 x (KLOC)1.05 Boehm simple model
E = 5.288 x (KLOC)1.047 Doty model for KLOC > 9
• FP-oriented models:
E = -13.39 + 0.0545 FP Albrecht and Gaffney model
E = 60.62 x 7.728 x 10-8 FP3 Kemerer model
E = 585.7 + 15.12 FP Matson, Barnett, and Mellichamp model
Basic COCOMO Model
• Construction Cost Model
• Heuristic Estimation technique assumes that relationship among
different parameters can be modeled using some mathematical
expression.
• Size is a primary factor for cost, other factors have lesser effect.
• Ranges in size from 2000 to 100000 LOC
• Based on waterfall model of software development.
• Post-architecture-stage model - Used during the construction of the
software.
• Organic: Developing well understood application programs, small
experienced team
• Semi Detached: mix of experienced and non experienced team,
unfamiliar
• Embedded: strongly coupled to computer hardware.

• Basic CoCoMO
• Effort = a1 (KLOC)a2 PM Time = b1 (Effort) b2 Months
• where a1 a2 b1 b2 are constants

You might also like