tag:blogger.com,1999:blog-3554166144204741789.post2992375192799607143..comments2023-12-31T02:16:32.747-08:00Comments on 1-800-MAGIC: Stories about Quality. 2. Why does software ship with bugs?Sergey Solyanikhttp://www.blogger.com/profile/03811112928687191837noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-3554166144204741789.post-19782188169587826212008-02-27T01:52:00.000-08:002008-02-27T01:52:00.000-08:00I want to share some insights about a recent surv...I want to share some insights about a recent survey results about software defects<BR/><BR/>.<BR/>1. Developers take 100 times less effort to find and fix a problem than one reported by a customer.<BR/>2. Half of software project work is wasted on unnecessary rework.<BR/>3. Twenty percent of the defects account for 80% of the rework.<BR/>4. Twenty percent of modules account for 80% of the defects and half the modules have no defects.<BR/>5. Ninety percent of the downtime comes from 10% of the defects.<BR/>6. Peer reviews catch 60% of the defects.<BR/>7. Directed reviews are 35% more effective than nondirected ones.<BR/>8. Discipline can reduce defects by 75%.<BR/>9. High-dependability modules cost twice as much to produce as low-dependability ones.<BR/>10. Half of all user programs contain nontrivial defects.<BR/><BR/>Software testing and analyzing source code using static tools will help developers to minimize the risks arising out of software defects. Companies like Symbian , Juniper networks ,Research in Motion(Blackberry),Cisco are using Coverity Prevent, a Static analysis code inspection tool for analyzing source code for fixing defects .<BR/> Coverity Prevent is also used by the Department of Homeland security to scan many open source projects. you can get more info at at http://www.Coverity.comvictor louishttps://www.blogger.com/profile/05965594516944149842noreply@blogger.comtag:blogger.com,1999:blog-3554166144204741789.post-50900818791973249962008-01-26T17:40:00.000-08:002008-01-26T17:40:00.000-08:00I like job to be fun too! But looks like 'fun' for...I like job to be fun too! But looks like 'fun' for me include doing my best to produce defect-free software. About 'too much time to do it' - one part of 'fun' for me is looking for ways to optimize this time... and this is VERY interesting research. :)<BR/><BR/>Anyway, I think you've answered my question about quality, thanks!Alex Efroshttps://www.blogger.com/profile/04974550881781378308noreply@blogger.comtag:blogger.com,1999:blog-3554166144204741789.post-61130588695765266622008-01-26T17:20:00.000-08:002008-01-26T17:20:00.000-08:00Well... it depends on application, doesn't it? I w...Well... it depends on application, doesn't it? I would really like that the software that's flying my plane has no (or very few) bugs. It is crucially important. To achieve it, people jump through enormous hoops, such as writing everything in Ada and having a lot of people developing very little code over a long time, but it's very reliable code.<BR/><BR/>On the other hand, I personally would not want to work for such a project (or even own the company that does it), because it is really, really boring.<BR/><BR/>On the other hand, take a commercially successful product such as Windows and iPhone. Both of them are buggy. They have just enough quality to do the work that people want them to do - most of the time. Would I want to own a company/manage the team that would own either as a product? Yes of course!<BR/><BR/>So I guess personally I am on the lax side of things - I like job to be fun, and producing code that has zero bugs is not - because it just takes too much time to do it. On the other hand, of course, I do not enjoy producing garbage either, and historically the code that I wrote was not branded as such...Sergey Solyanikhttps://www.blogger.com/profile/03811112928687191837noreply@blogger.comtag:blogger.com,1999:blog-3554166144204741789.post-81735218658300437752008-01-26T01:54:00.000-08:002008-01-26T01:54:00.000-08:00Yeah, this is current situation... So what you thi...Yeah, this is current situation... So what you think about it - is it OK for you? Personally for you, as developer and user? If not - do you've any ideas how to change this situation? :)Alex Efroshttps://www.blogger.com/profile/04974550881781378308noreply@blogger.comtag:blogger.com,1999:blog-3554166144204741789.post-78199665331766305972008-01-25T17:24:00.000-08:002008-01-25T17:24:00.000-08:00Imagine quality managment Yakuza way: one bug == o...Imagine quality managment Yakuza way: one bug == one finger. After you use voice interface it will be you head or prooff of gender : you choose. That might improve qualityAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-3554166144204741789.post-19368360679640923922008-01-25T17:19:00.000-08:002008-01-25T17:19:00.000-08:00Bugs in software is for job security... Of course ...Bugs in software is for job security... Of course this is a feature! Testers love devs for that reason: -)Anonymousnoreply@blogger.com