Group A3 – Beta Evaluation Report 3-6 pages, double-spaced, Times 12-point font; 1. Carefully review the SOP and evaluate how well the design meets the stated objectives. – Statement of Purpose (SOP) The SOP must clearly describe the collection, your target user, and objectives

Beta Evaluation Report

Group A3 – Beta Evaluation Report 3-6 pages, double-spaced, Times 12-point font; 1. Carefully review the SOP and evaluate how well the design meets the stated objectives. – Statement of Purpose (SOP) The SOP must clearly describe the collection, your target user, and objectives. The SOP does not describe the database, but rather what guided the design of the database. Address: What are the objects in the collection that the database records must represent? Who is the typical user? What does this user need to be able to do with the database? What would typical usage scenarios and queries be?

Beta Evaluation Report

The SOP needs to justify the design decisions you make. Keep in mind: the SOP will be used by your testers when they evaluate the database design; they will look to see if you met its stated objectives. 2. Evaluate the fields and their rules. 3. Add at least 5 records to the database, following the rules; this will help you to evaluate them. 4. Be sure to cover both commendations and recommendations in your report, in other words, describe what you found that was successful and what you found to be problematic.

Beta Evaluation Report

1. Address these questions in the report: How well did the designers meet the SOP’s stated objectives for the target user group? Is the design sufficient to meet the target user’s information needs? 2. How successful were the rules? Consider their clarity, how well they provided for consistency in the records, and how well they accommodated exceptions. 3. You may include other considerations and helpful comments for the designers.  https://youtu.be/VHSmb0RnwsM

Attached Files

Download  |