Dream Machine ( Build your own PC ) Message Board

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Dream Machine ( Build your own PC )

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: Spots who wrote (1492)	6/23/1998 12:55:00 PM
From: Sean W. Smith	Read Replies (1) of 14778

Every software release of each product contains a detailed list of problems fixed in the release and known remaining problems from every source (customer, reseller, qa, development, EAP, etc). This is part of the release documentation, also maintained in customer-accessible database and distributes on CD. Thats great but thats not reliability information its bug/feature lists. Where I work we do the same thing for all our products both hardware and software. Equivalent information to hardware reliability would be something like the following.... 1. Total Code Size Kloc 2. developement time 3. Total bugs killed during developement testing as a function of time and code size. 4. Total bugs killed after shipment per kloc per month.... 5. # of incidents reported of each bug per unit time. etc... Do you get the difference here. You want to know x of 1000 hw gadgets fail for x reason??? My point was to show that no-one hardware of software does this. Most reputable ahrdware software vendors have detailed release notes/revision historys but thats a totally different subject. do you understand? or do I need to explain further. Sean

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next