Software quality engineers can use this SQA checklist to ensure that the software in development passes standards set by the organization or regulating bodies. Assess the software’s performance, efficiency, and usability, and check for bugs, deficiencies, and security issues.
Digitalize this paper form now
Register for free on lumiformapp.com and conduct inspections via our mobile app
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?
Full name and signature of auditor
Please note that this checklist template is a hypothetical example and provides only standard information. The template does not aim to replace, among other things, workplace, health and safety advice, medical advice, diagnosis or treatment, or any other applicable law. You should seek your professional advice to determine whether the use of such a checklist is appropriate in your workplace or jurisdiction.
Please, finish the registration to access the content of the checklist.