Specification Attribute Checklist

• Compatible: Is anything missing or forgotten? Is it thorough? Does it include everything necessary to make it stand alone?
• Accurate: Is the proposed solution correct? Does it properly define the goal? Are there any errors?
• Precise, Unambiguous and Clear: Is the description exact and not vague? Is there a single interpretation? Is it easy to read and understand?
• Consistent: Is the description of the feature written so that it doesn't conflict with itself or other items in the specification?
• Relevant: Is the statement necessary to specify the feature? Is it extra information that should be left out? Is the feature traceable to an original customer need?
• Feasible: Can the feature be implemented with the available personnel, tools and resources within the specified budget and schedule?
• Code free: Does the specification stick with defining the product and not the underlying software design, architecture and code?
• Testable: Can the feature be tested? Is enough information provided that a tester could create tests to verify its operation?