Can Software Schedules Be Estimated? 480
"A recent academic paper Large Limits to Software Estimation (ACM Software Engineering Notes, 26, no.4 2001) shows how software estimation can be interpreted in algorithmic (Kolmogorov) complexity terms. An algorithmic complexity variant of mathematical (Godel) incompleteness can then easily be interpreted as showing that all claims of purely objective estimation of project complexity, development time, and programmer productivity are incorrect. Software development is like physics: there is no objective way to know how long a program will take to develop."
Lewis also provides a link to this "introduction to incompleteness (a fun subject in itself) and other background material for the paper."
Software Schedules (Score:4, Funny)
1) As long as it takes.
2) Take your best estimate , and double it and add 5 or something....
It prefer the as long as it takes. Other wise you end up with something like Windows Me.
Re:Double the number, add one and raise the unit! (Score:4, Funny)
Incompleteness (Score:3, Funny)
Lewis also provides a link to this "introduction to incompleteness" (a fun subject in itself)
I started writing a paper about this topic once, but I never finished it.
-WetDog
Actually.... (Score:3, Funny)
Re:Of course they can be estimated. (Score:5, Funny)
Re:Software Schedules (Score:2, Funny)
Everything takes longer than you expect, even when you take into account Hofstader's Law.
Re:Incompleteness (Score:1, Funny)
Re:Incompleteness (Score:2, Funny)
> started writing a paper about this topic once, but I never finished it.
Me t
Re:Slashdot readers are students? (Score:3, Funny)
Re:It's all a bunch of bull.. (Score:2, Funny)
He very carefully laid out the algorithm - I don't have my textbook handy, but it involved elementary mathematical operations on estimated man hours, estimated lines of code, estimated overhead, etc., then at the end -- and I am not making this up -- they multiply the result by a "magic number".
It hit me then that the whole discipline of estimating cost completion is all bullshit. You might as well be estimating with a crystal ball or divining the future with chicken bones. Since I've been working, the best advice I've gotten so far has been "take how long you think it'll take and double it".
Back when I was in middle school my math teacher told me that in order to calculate the area of a circle you had to square the radius and (I am not making this up!) multiply it by a magic number. They even had some hocus-pocus name for the magic number.
It was then that I new the entire field of mathematics had been invented by a bunch of wackos, and that my method was much better. I guess how large I think the area is and then double it. Works for me.
All equations with constants are obviously flawed.
Where did you hear such a thing? (Score:1, Funny)
We're all just normal geeks ...
No need to worry about those sirenes ...
It must be for your next door neighbour ...
Just stay where you are ...
There's nothing to worry about ...
Re:Of course they can be estimated. (Score:2, Funny)
Oh yeah, and while we are at it, it is no longer a bridge we want, it is a tunnel. And it doesn't cross the river any more, it is going to be used as a large wine cellar. And the 50million dollar budget is now 2 million, the 3 year estimate is now six weeks, we need you to use baseball bats and plastic spoons to dig the damn thing, oh yeah and when will it be ready ?
From the desk of BOFH (Score:1, Funny)
A good quote... (Score:2, Funny)
Magic 8 Ball Estimations (Score:2, Funny)
"Will this project be done in 8 weeks?"
shake "Outlook not good"
"OK, how about 12 weeks?"
shake "Maybe"
"Hmmm. Let's make it 15 to be sure..."
shake "Yes"
"Yep, this project will take 15 weeks."
And it really annoys managers when they discover that you used a Magic 8 Ball, and then it confounds them when it is right...
Re:Software Schedules (Score:3, Funny)
Standard estimate (Score:4, Funny)
Deadline estimate (Score:2, Funny)
incorrect. A very flexible deadline? Maybe...