Software Development Cycle

  1. Programmer produces code he believes is bug-free.
  2. Product is tested. 20 bugs are found.
  3. Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren’t really bugs.
  4. Testing department finds that five of the fixes didn’t work and discovers 15 new bugs.
  5. Repeat three times steps 3 and 4.
  6. Due to marketing pressure and an extremely premature product announcement based on overly-optimistic programming schedule, the product is released.
  7. Users find 137 new bugs.
  8. Original programmer, having cashed his royalty check, is nowhere to be found.
  9. Newly-assembled programming team fixes almost all of the 137 bugs, but introduce 456 new ones.
  10. Original programmer sends underpaid testing department a postcard from Fiji. Entire testing department quits.
  11. Company is bought in a hostile takeover by competitor using profits from their latest release, which had 783 bugs.
  12. New CEO is brought in by board of directors. He hires a programmer to redo program from scratch.
  13. Programmer produces code he believes is bug-free…
  • Share/Bookmark

Related Posts

This entry was posted on Thursday, February 5th, 2009 at 9:26 pm under , . You can leave a response here.

4 Responses to “Software Development Cycle”

  1. Skin pigmentation Says:
    February 17th, 2009 at 9:13 pm

    thanks of such useful info about software life cycle.

  2. Manas Says:
    February 20th, 2009 at 12:40 am

    Really? Just about 500 bugs in the whole product? That would be a really nicely written product dude! :)

  3. sp2hari Says:
    February 20th, 2009 at 12:55 am

    he he :) depends on the LOC too right? How about 500 bugs in a product where LOC = 500 :P

  4. Praveen j Says:
    February 26th, 2009 at 9:01 am

    Hareeeee, so you are still doing well online. I am not able to get some good time to do this. This one was good I thought. :)

Leave a Reply