Information System Requirement Checklist

Only available on StudyMode
  • Topic: Input, Usability, Transaction processing
  • Pages : 5 (666 words )
  • Download(s) : 410
  • Published : December 5, 2011
Open Document
Text Preview
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. f. System does not accept fixed field entries that are not appropriate to its description or label. g. System can recover in a fast and proper manner after a failure.

IV. PERFORMANCE
1. System has efficient design.
a. Response time is acceptable. (not more than 3 seconds) b. The system does not hang or encounters deadlock.
c. Database is normalized.
d. Correct definition of primary unique keys.
e. There are no wasted screen spaces.
f. Absence of databases and/or screen objects without any use or function.

V. SUPPORTABILITY
1. System is supportable.
a. System is maintainable by end-user.
b. System is easy to configure.
c. All required libraries have been incorporated in the installer kit.

VI. SECURITY
1. System is secure.
a. Unauthorized users cannot access the system.
b. Valid users can be properly defined. (with working user maintenance module) c. Valid user’s access level can be properly defined (with working user level definition module) d. Non-owners of module cannot create, edit or delete records. e. Individual users can change own passwords.

f. There is log/trail to audit user activities.

Polytechnic University of the Philippines
College of Computer Management and Information Technology
Sta. Mesa, Manila

Systems Software Development (SSD)
Rating Sheet
Criteria for Oral Defense
|Grading: | |Grade |Equivalent |Grade |Equivalent | |1.0 |Excellent |2.50 |Satisfactory | |1.25 |Excellent |2.75 |Satisfactory | |1.50...
tracking img