On 09/05/07, Richard Gaskin <[EMAIL PROTECTED]> wrote:
It started out with an interest in cyclomatic complexity, tailoring
McCabe's algorithm to be more appropriate for Rev (for example, I weight
"send...in time" since it's one of the few ways you can introduce race
conditions into Rev code, and
David Bovill wrote:
Whats a slam-dunk?
It's an American colloquialism derived from basketball, referring to
scoring a solid point in one decisive move (slamming the ball through
the hoop).
What sort of tools are you thinking of here Richard? I am asking because I
still have the code graphing
More seriously
On 09/05/07, Richard Gaskin <[EMAIL PROTECTED]> wrote:
But since most of my works spans multiple versions of products, I've
been fleshing out some internal tools for code base analysis,
What sort of tools are you thinking of here Richard? I am asking because I
still have t
Whats a slam-dunk?
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
Thanks for the input, Chipp and David.
I think David summed it up well here:
I have not looked at Function Point Analysis before - but reading up on it
makes doesn't leave a good taste.
For me this is more of a thought experiment than an immediate need, as I
have a small number of multi-year
I have not looked at Function Point Analysis before - but reading up on it
makes doesn't leave a good taste. Research shows that a huge percentage of
initial requirements (ie function points) never reach the final product -
from memory and the published research I read on this last year thi
Nope, don't use Function points here. But I do have experience in estimating
project scope. Here's some ideas:
1) First, get a small upfront check to build the spec. A defined spec will
help greatly in creating an estimate for what it takes to complete a
project. I typically like to cr
most popular is counting function points, but as I've looked
into this it seems that even the best methods for counting function
points have a strong subjective element (when is a particular input
considered "complex"?). So while I can see the value for large shops
where the sam