Re: First day with production development on D2005
- From: Larry Drews <larryd@<nospam>midfinance.com>
- Date: 3 Jun 2005 10:18:12 -0700
"Uwe" <forspammers@xxxxx> wrote in news:42a089b8@xxxxxxxxxxxxxxxxxxxxxx:
> Larry
>
> Don't get me wrong - I am all *for* the reporting of bugs. But I'm
> also convinced that an expensive product must be thoroughly tested
> before it is released and should have the highest quality possible.
> There's a fine line between expecting your customers to report bugs
> which are hard to find (that's absolutely okay with me), and expecting
> that your customers accept a product which is full of bugs which can
> be easily tracked if testing would have been done right the first
> time. To me, the latter is called "keeping your costs for QA" down by
> shifting them to your clients. Coming back to my car example: It would
> be fine with me if I have to deal with a defect which is hidden deep
> in the engine, but I wouldn't accept 4 missing tyres because they are
> so obvious.
>
> Cheers
> Uwe
>
Uwe,
I am basically in agreement with you. The only question is where does
Borland draw the line between additional QA testing and release? IMO
with a product as complex as Delphi (or other large software products)
it almost impossible to do as thorough a QA on the product within a
reasonable time frame and budget as either of us would desire. And
release to the field will still turn up "obvious" bugs that the QA
people did not write test cases for. And if Borland were to attempt to
significantly improve the level of QA testing, the cost of the product
and the time to release would both also increase. The people who do a
really good job at getting the bugs out, Boeing Avionics for example,
spend $2 for testing for every $1 of software development. Assuming
that a similar ratio would hold for a similar level of quality, I would
expect the price of Delphi to at least double or triple. Would you be
willing to pay, e.g., $3,000 for the Pro edition of Delphi, or $7500 for
the Enterprise edition. Lots of people already complain about the
price, I can only imagine the level of noise that such prices would
cause!
I for one think that Borland is doing a fairly reasonable job within the
constraints that it faces. I am willing to live with the bugs in order
to get as good a quality as I do get within the time frames that occur.
Otherwise I would have to switch to another product/vendor (and likely
experience exactly the same problem), and that would be heart-breaking.
I really do like Delphi!
Regards,
Larry
.
- Follow-Ups:
- Re: First day with production development on D2005
- From: Uwe
- Re: First day with production development on D2005
- From: Joe Hendricks
- Re: First day with production development on D2005
- References:
- First day with production development on D2005
- From: Atle Smelvær
- Re: First day with production development on D2005
- From: Alvaro GP
- Re: First day with production development on D2005
- From: Bruce McGee
- Re: First day with production development on D2005
- From: Alvaro GP
- Re: First day with production development on D2005
- From: Larry Drews
- Re: First day with production development on D2005
- From: Gerard
- Re: First day with production development on D2005
- From: Larry Drews
- Re: First day with production development on D2005
- From: Gerard
- Re: First day with production development on D2005
- From: Larry Drews
- Re: First day with production development on D2005
- From: Uwe
- Re: First day with production development on D2005
- From: Larry Drews
- Re: First day with production development on D2005
- From: Uwe
- First day with production development on D2005
- Prev by Date: Re: What can .Net do for me?
- Next by Date: Re: First day with production development on D2005
- Previous by thread: Re: First day with production development on D2005
- Next by thread: Re: First day with production development on D2005
- Index(es):
Relevant Pages
|
|