Information System Requirement Checklist
INFORMATION SYSTEM REQUIREMENT CHECKLIST
I. FUNCTIONALITY 1. Presence of required and/or expected functions and capabilities a. Reports/queries that should be generated/included. b. Reference file maintenance modules that should be included. c. Transaction processing that should be included. 2. System can proceed to the next task or process. 3. Absence of logical error or incorrect output. a. Correct computations/output. b. Function/button performs intended task (add, edit, delete, archive, deactivate, view, print, etc.) c. Correct data generated from input parameters. 4. Exceptions are handled properly. a. Input of numbers or date on character fields. b. Input of character (non-numeric) on numeric fields. c. Input of character and/or numbers (non-date) on date fields. d. Disallowing mandatory fields to be null. e. Duplicate records. (Ex. Same student, 2 student numbers)
II. USABILITY 1. Interface is user-friendly. a. Consistent naming of objects (buttons, forms, etc.) b. Consistent positioning of objects (buttons, functions, windows, etc.) c. Readable screen objects (labels, titles, names, etc.) d. Appropriate input mechanism/object used (ex. Radio button vs dropdown list) e. Objects have proper title, label, heading and sub-heading. f. If possible, reports have proper page totals and grand totals. g. Appropriate type of fonts, background and color used. h. Proper sequence of object activation (tabs)
III. RELIABILITY 1. System is reliable. a. The system quits in a regular manner. b. System behavior is consistent. c. System provides appropriate messages. d. Records in reference files that are used by transaction records cannot be edited without proper authorization and data reconciliation. e. Inactive records can be activated/deactivated without being physically deleted from table.
I. FUNCTIONALITY 1. Presence of required and/or expected functions and capabilities a. Reports/queries that should be generated/included. b. Reference file maintenance modules that should be included. c. Transaction processing that should be included. 2. System can proceed to the next task or process. 3. Absence of logical error or incorrect output. a. Correct computations/output. b. Function/button performs intended task (add, edit, delete, archive, deactivate, view, print, etc.) c. Correct data generated from input parameters. 4. Exceptions are handled properly. a. Input of numbers or date on character fields. b. Input of character (non-numeric) on numeric fields. c. Input of character and/or numbers (non-date) on date fields. d. Disallowing mandatory fields to be null. e. Duplicate records. (Ex. Same student, 2 student numbers)
II. USABILITY 1. Interface is user-friendly. a. Consistent naming of objects (buttons, forms, etc.) b. Consistent positioning of objects (buttons, functions, windows, etc.) c. Readable screen objects (labels, titles, names, etc.) d. Appropriate input mechanism/object used (ex. Radio button vs dropdown list) e. Objects have proper title, label, heading and sub-heading. f. If possible, reports have proper page totals and grand totals. g. Appropriate type of fonts, background and color used. h. Proper sequence of object activation (tabs)
III. RELIABILITY 1. System is reliable. a. The system quits in a regular manner. b. System behavior is consistent. c. System provides appropriate messages. d. Records in reference files that are used by transaction records cannot be edited without proper authorization and data reconciliation. e. Inactive records can be activated/deactivated without being physically deleted from table.