# Erroneous DPMO calculation

Six Sigma – iSixSigma Forums Old Forums Software/IT Erroneous DPMO calculation

Viewing 5 posts - 1 through 5 (of 5 total)
• Author
Posts
• #26281

Jiten
Participant

I work for a Leading banking company in US. While calcaluating DPMO of delivered software product often the capability calculation comes out to be misleading due to various interpretation of Opportunity to defect. Is it a line of code(LOC), or transactions or ?
Capability level is either exaggarated or is under calculated due to variuos assumtions.
What is the unit that is often recommended for a software product?

0
#63864

Bob J
Participant

Jiten,A couple of quick thoughts….A lot of current thinking in software development involves similar sizing issues, typically for level of effort estimates…  Research there might give you some insight…Check out Albrecht function point and McCabe Cyclomatic complexity in google…  Both are fairly easy to do and far more precise than LOC (and avoids all those issues with how do you count a line of code, ie commented?, frameworks?, etc)Hope this helps…Best Regards,Bob J

0
#63881

G
Member

Hi ,
In the world of computing where Quality is a big word to cater the need of a client and satisfy him, there r various ways to attain it.I have potrayed some of my ideas–

time=a(effort)^b
where,effort=person in monthstime= development time (including the design till testing)/man hours
a,b constants defined as per the system
System
1.Organic       —-     a=2.5   b=0.382.Semi-Detached —-     a=2.5   b=0.353.Embedded      —-     a=2.5   b=0.32
This is the COCOMO model formula used to translate the estimate of total effort put into an actual schedule.
But however i personally feel that the software cannot be evaluated by the LOC or Man Hours or Delivery procedures or Number of functions etc etc because its fully dependent on the language and technology that a developer works with alongwith the tools and services provided for the same.
But for sure the FP is very effective in determining the input from user,Reports,errors,bugs,db/connections.Formula for it —
FP = Total Count * [0.65 + .01*Sum(Fi)]
where Fi (i=1 to 14) are complexity adjustment values.

The other thing that i can think of is portraying through graphs and preparing the graphical analysyis of time consumed ,efforts putforth etc etc and preparing a chart, based on organisation procedures.This should be done by the effective and well trained quality people for the upliftment of the software and provide the ultimate quality to the client.

Thanks !!!
Santosh.

0
#63882

G
Member

Hi ,
In the world of computing where Quality is a big word to cater the need of a client and satisfy him, there r various ways to attain it.I have potrayed some of my ideas–

time=a(effort)^b
where,effort=person in monthstime= development time (including the design till testing)/man hours
a,b constants defined as per the system
System
1.Organic       —-     a=2.5   b=0.382.Semi-Detached —-     a=2.5   b=0.353.Embedded      —-     a=2.5   b=0.32
This is the COCOMO model formula used to translate the estimate of total effort put into an actual schedule.
But however i personally feel that the software cannot be evaluated by the LOC or Man Hours or Delivery procedures or Number of functions etc etc because its fully dependent on the language and technology that a developer works with alongwith the tools and services provided for the same.
But for sure the FP is very effective in determining the input from user,Reports,errors,bugs,db/connections.Formula for it —
FP = Total Count * [0.65 + .01*Sum(Fi)]
where Fi (i=1 to 14) are complexity adjustment values.

The other thing that i can think of is portraying through graphs and preparing the graphical analysyis of time consumed ,efforts putforth etc etc and preparing a chart, based on organisation procedures.This should be done by the effective and well trained quality people for the upliftment of the software and provide the ultimate quality to the client.

Thanks !!!
Santosh.
[email protected]
91-9886147121

0
#63885