You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I believe there is a mistake in the effort base factor value used in COCOMO calculations. I believe you use the default values from sloccount's "organic" mode, which sets this as 2.4, but scc's calculations use 3.2. Is this intentional or should it be 2.4?
It also looks like you used 1.8 as the "overhead" value when determining cost, as opposed to sloccount's default of 2.4.
Hah seems like I did make a mistake there. From memory I compared against sloccount's cost value and not anything else, but with the new values put in...
Original
Estimated Cost to Develop $6,300,654
Estimated Schedule Effort 30.878580 months
Estimated People Required 24.170352
Revised
Estimated Cost to Develop $6,300,654
Estimated Schedule Effort 27.680925 months
Estimated People Required 20.221854
Describe the bug
I believe there is a mistake in the effort base factor value used in COCOMO calculations. I believe you use the default values from
sloccount
's "organic" mode, which sets this as 2.4, butscc
's calculations use 3.2. Is this intentional or should it be 2.4?It also looks like you used 1.8 as the "overhead" value when determining cost, as opposed to
sloccount
's default of 2.4.See:
https://dwheeler.com/sloccount/sloccount.html#cocomo
https://github.com/boyter/scc/blob/master/processor/cocomo.go#L18
The text was updated successfully, but these errors were encountered: