DECOMPOSITION

TECHNIQUE

By
Janani.M
II Mcom (FCA)
 Decomposition Technique
 Software project estimation is
a form of problem solving, and in most cases, the
problem to be solved (i.e., developing a cost
and effort estimate for a software project) 

 For this reason, we decompose the problem, re-
characterizing it as a set of smaller
The decomposition approach was discussed from
two different points of view:

 decomposition of the problem

 decomposition of the process.

Estimation uses one or both forms of partitioning.

 Software Sizing
The accuracy of a software project estimate is predicated on a number of things: 

 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 (a function of the availability of reliable software metrics from past
projects)

  The degree to which the project plan reflects the abilities of the software
team

 The stability of product requirements and the environment that supports

 Explanation
 Sizing represents the project planner’s first major
challenge.

 If a direct approach is taken, size can be

measured in LOC. If an indirect approach is
chosen, size is represented as FP.
 FOUR DIFFERENT APPROACHES
TO THE SIZING PROBLEM
Putnam and Myers  suggest four different approaches to
the sizing problem:

 “Fussy logic”sizing: To apply this approach, the

planner must identify the type of application, establish
its magnitude on a qualitative scale, and then refine the
magnitude within the original range

 Function point sizing. The planner develops estimates

of the information domain characteristics.
 Conti……
 Change Sizing: The planner estimates the number and
type (e.g., reuse, adding code, changing code, deleting
code) of modifications that must be accomplished.

 Standard component sizing. Software is composed of a

number of different “standard components” that are
generic to a particular application area. For example, the
standard components for an information system are
subsystems, modules, screens, reports, interactive
programs, batch programs, files, LOC, and object-level
instructions.
 Advantages and Disadvantages of
Decomposition Technique
 You have to really understand the problem you're
trying to solve to be able to decompose it
properly. Otherwise you'll end up writing code
you don't need.

 Teams have to work together really effectively

when they are working on their own sections of a
program. Otherwise the parts won't fit together
properly
 I find that using decomposition means that my programs
often end up being shorter on the whole.

 The sections of a program are sometimes called

subroutines or functions

 Decomposition is when I break up a program into small

sections.

 Different people can code the sections of decomposed

program at the same time. This makes writing a
complex program quicker as the jobs can be divided up
more easily