Comments on: Where Bugs Come From http://tynerblain.com/blog/2006/01/22/where-bugs-come-from/ Software product success. Tue, 16 Mar 2010 02:37:05 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: lean manufacturing software http://tynerblain.com/blog/2006/01/22/where-bugs-come-from/comment-page-1/#comment-282365 lean manufacturing software Thu, 31 Jan 2008 09:07:28 +0000 http://tynerblain.com/blog/2006/01/22/where-bugs-come-from/#comment-282365 <strong>lean manufacturing software...</strong> We have very much promoted this type of business practice ourselves and am glad I came across your blog again. I have added you to our digg bookmarking account. Thanks!... lean manufacturing software…

We have very much promoted this type of business practice ourselves and am glad I came across your blog again. I have added you to our digg bookmarking account. Thanks!…

]]> By: Software requirements - process and roles -Tyner Blain http://tynerblain.com/blog/2006/01/22/where-bugs-come-from/comment-page-1/#comment-285 Software requirements - process and roles -Tyner Blain Tue, 14 Feb 2006 00:25:26 +0000 http://tynerblain.com/blog/2006/01/22/where-bugs-come-from/#comment-285 [...] Note that there are also steps involved in assuring the quality of the solution, and feedback loops in a good software development process. We covered this in our earlier post, Where bugs come from. We’ve also talked in more detail about the software development process in our post, Describing the software development process. In order to keep this discussion on task, we’ve simplified our presentation of that material in this post. [...] [...] Note that there are also steps involved in assuring the quality of the solution, and feedback loops in a good software development process. We covered this in our earlier post, Where bugs come from. We’ve also talked in more detail about the software development process in our post, Describing the software development process. In order to keep this discussion on task, we’ve simplified our presentation of that material in this post. [...]

]]> By: Software testing series: Top three measurements of quality -Tyner Blain http://tynerblain.com/blog/2006/01/22/where-bugs-come-from/comment-page-1/#comment-207 Software testing series: Top three measurements of quality -Tyner Blain Fri, 03 Feb 2006 03:40:23 +0000 http://tynerblain.com/blog/2006/01/22/where-bugs-come-from/#comment-207 [...] This developer perspective is a little misleading, however. To developers, if the software performs according to the spec, it meets the requirements, and is therefore good software. To a product manager, this could represent one of several requirements writing mistakes - the missing behavior should be there but it isn’t, because it was not documented in the spec. In short, the source of this bug is in the requirements. [...] [...] This developer perspective is a little misleading, however. To developers, if the software performs according to the spec, it meets the requirements, and is therefore good software. To a product manager, this could represent one of several requirements writing mistakes – the missing behavior should be there but it isn’t, because it was not documented in the spec. In short, the source of this bug is in the requirements. [...]

]]> By: Requirements and software development process and where bugs come from --Tyner Blain http://tynerblain.com/blog/2006/01/22/where-bugs-come-from/comment-page-1/#comment-140 Requirements and software development process and where bugs come from --Tyner Blain Wed, 25 Jan 2006 00:36:48 +0000 http://tynerblain.com/blog/2006/01/22/where-bugs-come-from/#comment-140 [...] [Ed: This post was retitled, edited, and updated as Where bugs come from due to recurring issues for some readers with accessing this page. Please read the updated version (there are some revisions to the content and new links to other content). Thanks] [...] [...] [Ed: This post was retitled, edited, and updated as Where bugs come from due to recurring issues for some readers with accessing this page. Please read the updated version (there are some revisions to the content and new links to other content). Thanks] [...]

]]> By: Software testing series: Introduction --Tyner Blain http://tynerblain.com/blog/2006/01/22/where-bugs-come-from/comment-page-1/#comment-139 Software testing series: Introduction --Tyner Blain Wed, 25 Jan 2006 00:34:38 +0000 http://tynerblain.com/blog/2006/01/22/where-bugs-come-from/#comment-139 [...] We can analyze the costs (and benefits) of testing. We can make our tests efficient to run, or focus on minimizing their maintenance costs. We can apply theory to identify what to test and use statistics to characterize the quality of software. We can try to understand where bugs come from. In our series, we will touch on many of these topics and link to some of the better articles from experts out there. [...] [...] We can analyze the costs (and benefits) of testing. We can make our tests efficient to run, or focus on minimizing their maintenance costs. We can apply theory to identify what to test and use statistics to characterize the quality of software. We can try to understand where bugs come from. In our series, we will touch on many of these topics and link to some of the better articles from experts out there. [...]

]]> By: Tyner Blain » Fixing the requirements mess http://tynerblain.com/blog/2006/01/22/where-bugs-come-from/comment-page-1/#comment-130 Tyner Blain » Fixing the requirements mess Sun, 22 Jan 2006 21:33:29 +0000 http://tynerblain.com/blog/2006/01/22/where-bugs-come-from/#comment-130 [...] Stephen Larrison posted an article in his blog, Survive Outsourcing, about how to compete with offshore-outsourced projects by fixing the requirements mess up front. His background in manufacturing, as well as software development has lead him to a similar perspective as the one I touched briefly on in my post about where bugs come from. [...] [...] Stephen Larrison posted an article in his blog, Survive Outsourcing, about how to compete with offshore-outsourced projects by fixing the requirements mess up front. His background in manufacturing, as well as software development has lead him to a similar perspective as the one I touched briefly on in my post about where bugs come from. [...]

]]>