Scribd
Upload
6 views

SPM UNIT-2 (Lecture-2)

The document discusses decomposition techniques for software project estimation, emphasizing the divide and conquer approach to estimate cost, time, and efforts. It outlines methods such as Software Sizing, Problem-based Estimation, and Process-based Estimation, along with empirical techniques like Expert Judgement and Delphi cost estimation. Each method includes specific approaches and considerations for accurate project estimation.

Uploaded by

suryakantshastri.gn
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
6 views

SPM UNIT-2 (Lecture-2)

The document discusses decomposition techniques for software project estimation, emphasizing the divide and conquer approach to estimate cost, time, and efforts. It outlines methods such as Software Sizing, Problem-based Estimation, and Process-based Estimation, along with empirical techniques like Expert Judgement and Delphi cost estimation. Each method includes specific approaches and considerations for accurate project estimation.

Uploaded by

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

Software Project Management

UNIT-2
Lecture-2

Decomposition Techniques
 Software Project Estimation is a form of problem solving (To estimate cost, time & efforts in
software project.)
 Decomposition Technique is divide & conquer approach of Software Project Estimation.
 By decomposition a project into major functions like software engineering related activities,
cost, schedule & efforts estimation can be performed in stepwise manner.
Decomposition Techniques are:
1. Software Sizing
2. Problem based Estimation
3. Process based Estimation

1. Software Sizing
Sizing represents the project planner's first major challenge.
 The accuracy of a software project estimate is predicated on a number of things:
1. The degree to which the planner has properly estimated the size of the product to be built.
2. The ability to translate the size estimate into human effort, calendar time and dollars.
3. The degree to which the project plan reflects the abilities of the software team.
4. The stability of product requirements & environment that supports software engineering
effort.
Approaches of Software Sizing:
1. "Fuzzy Logic" Sizing
2. Function Point Sizing
3. Standard Component Sizing
4. Change Sizing
Approaches of Software Sizing
Putnam and Myers suggest four different approaches of Software Sizing Problem:
1. "Fuzzy Logic" Sizing:
 To apply this approach, the planner must identify the type of application.
 Although personal experience can be used, the planner should also have access to historical
 database of projects so that estimates can be compared to actual experience.

2. Function Point Sizing:


 The planner develops estimates of the information domain characteristics.

3. Standard Component Sizing:


 Standard components for an information system are subsystems, modules, screens, reports.
interactive programs, batch programs, files, LOC and object-level instructions.
 Uses historical project data to determine the delivered size per standard component.
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 reuse, adding code, changing code, deleting code of modifications
that must be accomplished.
 Using an "effort ratio" for each type of change, the size of the change may be estimated.

2. Problem based Estimation


 Lines of code and function points were described as measures from which productivity
metrics can be computed. (LOC/pm & FP/pm)
 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.
2. As baseline metrics collected from past projects and used in conjunction with estimation
variables to develop cost and effort projections.
3. A three-point or expected value can then be computed
S= (Sopt + 4Sm+ Spess)/6
Were,
S = expected-value for the estimation variable (size)
Sopt =optimistic value
Sm=most likely value
Spess = pessimistic value

3. Process based Estimation


Most common technique for estimating project is to 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.
 Once problem functions & process activities are decided, the planner estimates the effort
(e.g., person-months) that will be required to accomplish each software process activity for
each software function.
 Average labor rates (cost/unit effort) are then applied to the effort estimated for each process
activity.
 It is very likely the labor rate will vary for each task.
 Senior staff heavily involved in early activities are generally more expensive than junior

Empirical Estimation Technique:


Empirical estimation technique is based on the data taken from the previous projects and some based
on guesses and assumption.
There are many empirical models but most popular are
1. Expert judgement techniques
2. Delphi cost estimation
1. Expert judgement Techniques
 An expert makes an educated guess of the problem size after analysing the problem
thoroughly.
 Expert estimate the cost of different component i.e., module and submodules of the
system.
 Estimation by group of experts minimizes factor’s such as individual oversight, lack
of familiarity with a particular aspect of a project, personal bias, and the desire to win
contract through overly optimistic estimates.

Disadvantages:
1. Human error
2. Considering not all factors and aspect of the projects.
3. Individual bias
4. More change of failure

2. Delphi cost estimation:

Estimation by = expert group + coordinators

Role of members
Coordinators provide a copy of software requirement specification (SRS) document and a
form of recording his cost estimate to each estimator.

Estimators- estimators complete their individual estimates and submit to the coordinators
with mentoring, if any, unusual characteristic of product which has influenced his estimation.

The coordinator prepares and distributes the summery of the response to all estimators and
they re-estimate them.

 No discussion is allowed among the estimators during the entire estimation process
because they may be many estimators get easily influenced by ratio of an estimator
who may be more experienced or senior.
 After the completion of several iterations of estimators, the coordinators take the
responsibility of compiling the result the final estimates.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy