The document discusses testing and evaluating databases. It describes query testing by comparing predicted and actual query results to check for errors. It also discusses fitness for purpose by ensuring the database meets client, specification, and end-user requirements. Finally, it notes that ensuring fitness for purpose does not guarantee accuracy, and output must be tested to ensure correctness and expected outcomes.

1. Testing and Evaluation of
Databases

2. Query Testing
 A query gives the user a set of answers based on certain conditions set.
 The predicted result should be recorded along with the actual result from
running the query.
 The results from both should be compared and if not the same then the
database will need to be changed/updated and the query design checked.

3. Fitness for Purpose
 If the database created meets the requirements of the client.
 If the database meets the specification and functional requirements (from the Analysis
phase).
 If the database meets the end-user requirements.
 If the database does not meet these requirements then phases of the development
process need to be revisited.

4. Accuracy of Output
 Ensuring the database is fit for purpose does not always ensure the correct
output.
 To ensure the database is working correctly, the output needs to be
correct and give the user the expected outcome.
 This is called accuracy of output.