This was a self-initiated project sparked by seeing how inefficient and mistake-prone testing could be, even with clear regulation-based guidelines. Some common problems came from turnover in the testing workforce, the sheer volume of test items, the volume and variety of test data, and the frequency of delays during the tests.
My proposed database-backed system would take advantage of the formalized guidelines to make the testing process run on rails, and would thus solve the just-listed problems.
UPDATE 1: Speaking of rails, as I researched the best way to implement the system, I got a taste of the future when my research took me to the Ruby on Rails project; I could see that web-based approach was certainly the best solution.
UPDATE 2: Looking back from early 2013, I can also now see that tablet-like devices would have been (and still would be) the ideal hardware to match with the software described/shown. On-the-floor testing makes even notebook-type solutions awkward, but a direct touch-based interface running on a small tablet would be just right.
