Jump to content

Estimating Software Size - Can We Still Do It?


Recommended Posts

I keep seeing versions of this article popping up in my Google alerts. When I look for the original (Galorath.com), I only get a 404. Hmm.....

The article discusses LabVIEW and GOOP, so I thought it was worth sharing.

I like this paragraph:

The software community has made great progress in creating tools to improve productivity – but our estimates are wrong because we stopped half way! We need to regroup and identify software size as it relates to software cost and involve parametric tools to calculate accurate estimates. Until then – it’s purely guess work to estimate new product development and blind trust in tribal knowledge when modifying existing applications. How long does it take to make GOOP?

( We now return you to your regularly scheduled 'Alfa String' RSS feed :P )

Edited by Phillip Brooks
  • Like 1
Link to comment

That is a great question, and probably the most difficult I have had to answer on numerous occasions in my career.

I'm no expert but I have gotten a lot better coming up with reasonable estimates on how long it will take me to write some code. And I'm not intimidated any more when my boss(es) and planners and account managers in the meeting room let out a collective "GASP!" when I say "oh, about 3 months." rolleyes.gif

What always ends up biting me in the @ss is something hardware related.

Every. Single. Time.

Whether it's drivers or compatibility or mechanical, or availability or cleaning up someone else's mess it's always hardware related. Trying to fit a square pin into a round hole accounts for 90% of my wasted time. angry.gif

Link to comment

What always ends up biting me in the @ss is something hardware related.

Yes!

I hate it when some project manager comes knocking on the door asking me to write code for a VXI system. And yes, they gasp when I tell them how long it will take. Then I tell them about 10% of that is writing code and the rest of it is a science project getting all the cards to play well together on whatever system they need it to work on.

And don't get me started about working with SCSI...

Link to comment

Yes!

I hate it when some project manager comes knocking on the door asking me to write code for a VXI system. And yes, they gasp when I tell them how long it will take.

Ah, yes. military projects still love VME/VXI. I Wrote LabVIEW wrappers for two different VME controller cards; each with their own API to the Tunda. The first controller was unreliable and the second was unavailable.

We finally ditched the whole design. It was about that time that we upgraded to 8.20 and found out that we could have used the import DLL wizard to do much of what had taken me months to do. :wacko: I haven't had to use my VMETRO knowledge since. Just checked and it appears that they were acquired by Curtiss Wright.

(woohoo! I've hit 365 posts. Is this my first Lava-versary?)

Edited by Phillip Brooks
Link to comment

... Then I tell them about 10% of that is writing code and the rest of it is a science project getting all the cards to play well together on whatever system they need it to work on ...

Yes!

Indeed. I wish I had more hardware folks I could count on. Or clones of myself to do it for me ... wink.gif

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.