Title Page

  • Site conducted

  • Conducted on

  • Project/Software Name

  • Software Owner/SME/SCCC

  • Prepared by (Software Quality Assurance Inspector/Auditor)

  • Location


  • This checklist references to IEEE 830:1998 (Recommended Practice for Software Requirement Specifications) and ISO/IEC/IEEE 29148:2018 (Systems and software engineering - life cycle processes - Requirements engineering) as guidance on the adequacy of the Software Requirement Specification (SRS). (this checklist is typically used as part of SQA inspections)Re

SRS Checklist

  • Has the Software Requirement Specification (SRS) or equivalent been established, reviewed and approved?

  • Is there an OpsCon document or SyRS to reference? (which specifies the software requirements)

  • Has other documentation been developed that should reference the missing documentation?

  • Does the software requirements conform to system / product requirements? Are they backward traceable?

  • Have the external interfaces (inputs and outputs) of the software been specified? (N/A for a software only project)

  • Have the functional requirements of the software been specified?

  • Have the non-functional requirements (eg. performance) of the software been specified?

  • Have the logical database requirements been specified?

  • Have the design constraints been specified?

  • Have the standards or regulatory documents, which the software must adhere to, been specified?

  • For the above questions, has each requirement been uniquely identified, complete, consistent, unambiguous, prioritized, traceable and testable?

  • List down the non-compliance:

  • Not uniquely identified?

  • Incomplete?

  • Ambiguous?

  • Not Prioritized?

  • Not Traceable?

  • Not Testable?

  • Process Verification - Are the activities during the requirements phase in line with the life cycle processes documented in the plans?

The templates available in our Public Library have been created by our customers and employees to help get you started using SafetyCulture's solutions. The templates are intended to be used as hypothetical examples only and should not be used as a substitute for professional advice. You should seek your own professional advice to determine if the use of a template is permissible in your workplace or jurisdiction. You should independently determine whether the template is suitable for your circumstances.