@boyter Ok, so after reviewing the original COCOMO I model, and researching the COCOMO II model, I realized that number of developers is not an input to the formula, but an output. I could not find the exact COCOMO II formula. So this question is sort of malformed, sorry.

Generally speaking, whatever the inputs are, is the desire of this feature request. So two questions remain to be answered:

Are you really using COCOMO II? In your code:

// EstimateEffort calculate the effort applied using generic COCOMO2 weighted values
func EstimateEffort(sloc int64) float64 {
	var eaf float64 = 1

	// Numbers based on organic project, small team, good experience working with requirements
	var effortApplied = float64(3.2) * math.Pow(float64(sloc)/1000, 1.05) * eaf
	return effortApplied
}

Please feel free correct me if I'm wrong, but this looks like the COCOMO I formula... E=a(KLOC)^b

If you are indeed using COCOMO II, then the inputs increase drastically!
COCOMOII But, you have to find the COCOMO II formula.

Uh oh!

Feature Request: Extend custom COCOMO parameters #188

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions