« Later entry | Main | Earlier entry »
November 26th, 2005

Requirements and Software Development Process and Where Bugs Come From

[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]

Please Rate This Article!
Just Plain BadLameAverageGoodGreat (2 votes, average: 4.5 out of 5)
Loading ... Loading ...

This article was published on Saturday, November 26th, 2005 at 5:09 am and is filed under Process Improvement, Requirements, Testing.
You can leave a comment on this post.
Trackback URL

Check out these related posts

One Response to “Requirements and Software Development Process and Where Bugs Come From”

  1. Software testing series: Black box vs white box testing -Tyner Blain Says:
    January 25th, 2006 at 5:55 pm

    [...] Hard to catch misinterpretation of requirements. Developers read the requirements. They also design the tests. If they implement the wrong idea in the code because the requirement is ambiguous, the white box test will also check for the wrong thing. Specifically, the developers risk testing that the wrong requirement is properly implemented. [...]

Join The Discussion

« Later entry | Main | Earlier entry »