January 8, 2010
In many projects this depends on the release criteria for the software. Such criteria are often in turn based on the decision to end testing. Unfortunately, for any but the simplest software projects, it is nearly impossible to adequately specify useful criteria without a significant amount of assumptions and subjectivity. For [...]
Read the full article →
January 8, 2010
One of the most reliable methods of ensuring problems, or failure, in a large, complex software project is to have poorly documented requirements specifications. (Note that requirements documentation can be electronic, not necessarily in the form of printable documents, and may be embedded in code comments, may be embodied in well-written test cases, etc.) Requirements [...]
Read the full article →