COCOMO - appropriate for languages like Python?

[James J. Besemer]

Andrae Muys wrote:

> "James J. Besemer" <jb at cascade-sys.com> wrote in message news:<mailman.1026198259.4647.python-list at python.org>...
> > From a management standpoint, your strategy should be to always strive to hire
> > the very best people and to break projects into moderate sized, easily handled
> > chunks.
> >
> > From a schedule estimation standpoint, LOC (however you choose to count them)
> > appears to be a pretty good estimator to use for a fixed staff and fixed project
> > sizes.  How the prediction varies as you change staff or project sizes is
> > something you'll have to measure or guess at yourself.  At least COCOMO research
> > gives you some idea how the curves are shaped.
> >
>
> Do you have any references where I could follow up on this myself?

The quoted exerpts above are merely my humble opinions, based on many many years of software development and software
development management.

If you google.search( COCOMO ) you get lots of references to past and ongoing work.

If you amazon.books.search( COCOMO ) I see there's now a COCOMO II.

This looks like a substantial update to Boehm's seminal Blue book on Software Engineering Economics.

Either of the above are good as any starting point.

Regards

--jb


--
James J. Besemer  503-280-0838 voice
http://cascade-sys.com  503-280-0375 fax
mailto:jb at cascade-sys.com