SRS Inspection Checklist
Short review guide for preparation before the inspection meeting
Use this checklist while reading the assigned SRS.
A. Requirement-Level Checks
• Is the requirement clear and unambiguous?
• Is it complete? Are conditions, limits, actors, inputs, and outputs clear?
• Is it verifiable or testable?
• Is it feasible within the known project scope?
• Is it atomic (one requirement), or does it combine multiple ideas?
• Does it avoid vague terms such as fast, user-friendly, efficient, secure, easy, quickly?
• Is it really a requirement, rather than a design or implementation choice?
• Does it conflict with or duplicate another requirement?
B. Document-Level Checks
• Are the main customer needs covered?
• Are both functional and non-functional requirements present?
• Are requirement IDs unique and used consistently?
• Is the terminology consistent throughout the document?
• Are diagrams readable, correct, and consistent with the text?
• Is there a table of contents and a logical section structure?
• Are assumptions, constraints, alternative flows, error conditions, and business rules clear?
C. Common Warning Signs
Watch for Why it matters
Words like fast / easy / user-friendly / efficient / Usually too vague unless measured or defined.
secure
One sentence that contains many shall Often not atomic; it may hide multiple
statements or many actions requirements.
A requirement that names a specific technology May be a design decision instead of a
or UI design immediately requirement.
Missing actor, condition, trigger, or error case May make the requirement incomplete or hard to
test.