A nice top down overview, but the devil can be in the details, and the top down may not catch those details.
For example: "data corruption."
Yes, it may be that devs might not be using "approved methods for accessing the database."
BUT - it might also be the case that data is being corrupted by the hardware.
This overview does not account for stuff like that.
"Peer reviews of the application?s design and code are effective in detecting defects that might otherwise slip past test cases written to verify compliance with functional requirements."
I'd argue that a good test suite should be creating higher quality code than peer reviewed code. If not, then I'd wonder about the quality of the test suite.
Discussion on:
The best of ZDNet, delivered
ZDNet Newsletters
Get the best of ZDNet delivered straight to your inbox
