I am sure that by now a lot of people who have been into development have experienced sets of problems whihch occur which consistency...(something like the 20 - 80 cause effect..) am thinking that we can create a database which can provide information regarding the same so that the quality of the work product can get better ..
There often are similar sets of consistently occuring problems across projects.
For example, "Row not found" errors (SQL100) often occur when the database returns a null query. However, the cause for this error could be different for each application. Did the query return no results because the system did not properly populate the database with the necessary data? Or was the query written incorrectly, so the data is there but the system couldn't find it? Or did the system properly query the database, and there really is no data there and that is correct?
On top of that, the way to produce these scenarios will be different in each application. In a web-based shopping cart you might test an order with no items in the shopping cart. Or you might try doing an inquiry on an invalid order number. In a search engine you might test a search that returns no results. Or you might do something else completely, that is unique to your application.
Subsequently, such checklists have to be general enough to be applicable to everyone (and sometimes lacking the details testers need.) A database of this sort could be quite helpful at the application level. For example, many organizations compile a repository of the common problems, build tests for each, and call it their regression test suite.
For further reading, here are some books which do a good job of addressing many common scenarios:
"Testing Computer Software" - Kaner, Nguyen, Falk.
"Lessons Learned in Software Testing" - Kaner, Bach, Pettichord.
I understand the purpose of the checklists. My proposal was to build a commom defects database which could be language based. (something on these lines.) am talking of the checklists at implementation level (of projects) like what is mentioned in the Quality Mgmt Plan at the project level.