Initial Preparation

An organizational policy has been established for QA activities?

All resources and funding secured for performing QA activities?

QA Team has received adequate training and appropriate qualifications?

The QA team has been oriented on QA roles, responsibilities, authority and values?

A project QA plan is prepared according to a documented procedure?


A peer-review schedule has been established and is being followed?

Checkpoint reviews have been established and are being followed?

Reviews and reports are being documented according to set procedure?

Deviations in activities and work products are identified, documented, and controlled according to an official procedure?

Software QA - Functionality

Does the software’s main function directly resolve the user’s primary need?

Is it consistent enough to address the user’s need with precision on a regular basis?

Are the software’s specific functions successful in meeting specific user needs?

Software QA - Efficiency

Do the software’s functions respond with reasonable speed considering the task being requested?

Does the software actively utilize its resources economically when tasked to fulfill functions?

Is the software’s functional limits within acceptable set requirements?

Software QA - Usability

Does the software define itself well enough for users to easily recognize if it is appropriate to their needs?

Is the difficulty of learning to use the software reasonable considering its intended functions and the user’s needs?

Is the software reasonably easy to use considering the function being utilized, and the user’s need?

Software QA - Security

Does the software ensure that confidential data is only accessible to authorized users?

Is the software capable of resisting unauthorized access attempts through program modification and other malevolent means?

Is the software capable of verifying the identity of an entity before allowing access?

Software QA - Maintainability

Is the software composed of a sufficient number of separate components that remain unaffected should another component be changed or altered?

Can the software handle reasonable modifications without suffering defects, malfunctions, and a drop in overall quality?

Is the software consistent and reliable enough so that test criteria can be established and accurate results can be retrieved?

Auditor Sign-off
Full name and signature of auditor
Please note that this checklist is a hypothetical example and provides basic information only. It is not intended to take the place of, among other things, workplace, health and safety advice; medical advice, diagnosis, or treatment; or other applicable laws. You should also seek your own professional advice to determine if the use of such checklist is permissible in your workplace or jurisdiction.