TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy


Options: Use Classic View

Use Proportional Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Mime-Version: 1.0
Content-Type: TEXT/PLAIN
Date: Wed, 12 Feb 1997 11:32:00 -0500
From: "(No Name Available)" <[log in to unmask]>
Content-Transfer-Encoding: 7BIT
Sender: "Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
Parts/Attachments: TEXT/PLAIN (19 lines)
   Capers Jones has lots of stats on language and function points and
   productivity rates -- see WWWeb at SPR.Com and his text.

   As he would tell you -- its better to estimate the functionality from user
   descriptions via function points than backfiring your SLOCs from language
   A into FPs and then using his tables to estimate the boundaries of the
   projected conversion.  If you read his text  "Applied Software
   Measurement" he outlines various factors which can drive up line counts

   Also from my experience with COCOMO projections, the effort levels are
   also quite resposive (read hyper) to the environmental cost drivers -- in
   a new/adapted environment you cannot assume the same environmental
   factors.  Even from a small maintenenace task to larger conversion you
   must reconsider some of the expertise-level factors.

   -- Mike Berens
   Lockheed Martin