This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

software quality - what do you use

just curious folks to what folk use to help develope their software with.

I am an avid user of lint and having a go at trying to design what i am gonna do before i start being a code monkey but would like to find out what others are using.

Recently downloaded Tessy but as i get the feeling trying to apply it to an exsisting project will be a huge project its self and as the vendors havent been rushing to reveal the price cost may be an issue.

Does anybody have any recomendations on tools they find useful?

Parents
  • what IBM seeks to patent has been a metric in many organizations for ages - agreed, somewhat imprecise. That Itty Bitty Machine Co has made a program should not allow them to patent the method

    Erik

    BTW the metric is ridiculous in many cases. You are to be judged on how many changes you make to something you have committed. How often have you been forced to commit against your better knowledge because "It has to go out the door today". I doubt very much the program IBM has made will take that into account. Also, you commit 'perfect' code and have to 'uncommit' because some spec changes, what about that.

    We have so many things that are made to make management believe they can schedule precisely (agile, waterfall, ....) they all have pros and cons, but all suffer from the illusion that software development time can be estimated precisely.

Reply
  • what IBM seeks to patent has been a metric in many organizations for ages - agreed, somewhat imprecise. That Itty Bitty Machine Co has made a program should not allow them to patent the method

    Erik

    BTW the metric is ridiculous in many cases. You are to be judged on how many changes you make to something you have committed. How often have you been forced to commit against your better knowledge because "It has to go out the door today". I doubt very much the program IBM has made will take that into account. Also, you commit 'perfect' code and have to 'uncommit' because some spec changes, what about that.

    We have so many things that are made to make management believe they can schedule precisely (agile, waterfall, ....) they all have pros and cons, but all suffer from the illusion that software development time can be estimated precisely.

Children