As I am about to use a number of these to try and identify weakenesses in our current requirements and documentation, I thought I would link them for the benefit of all - I'm not sure many people know these exist and are available online. They come from possibly the best book written on software development, Code Complete 2 by Steve McConnell

You can read the full list of checklists (a free and simple registration is required), but the ones I think are critical to the success of a project are from the Requirements Checklist. As Steve says, they may not be comprehensive, they may not be complete, they don't tell you how to do these things, it is just a good sanity checking list:

Specific Functional Requirements

• Are all the inputs to the system specified, including their source, accuracy, range of values, and frequency?
  
• Are all the outputs from the system specified, including their destination, accuracy, range of values, frequency, and format?
  
• Are all output formats specified for web pages, reports, and so on?
  
• Are all the external hardware and software interfaces specified?
  
• Are all the external communication interfaces specified, including handshak-ing, error-checking, and communication protocols?
  
• Are all the tasks the user wants to perform specified?
  
• Is the data used in each task and the data resulting from each task specified?
  

Specific Non-Functional (Quality) Requirements

• Is the expected response time, from the user's point of view, specified for all necessary operations?
  
• Are other timing considerations specified, such as processing time, data-transfer rate, and system throughput?
  
• Is the level of security specified?
  
• Is the reliability specified, including the consequences of software failure, the vital information that needs to be protected from failure, and the strategy for error detection and recovery?
  
• Is maximum memory specified?
  
• Is the maximum storage specified?
  
• Is the maintainability of the system specified, including its ability to adapt to changes in specific functionality, changes in the operating environment, and changes in its interfaces with other software?
  
• Is the definition of success included? Of failure?

Requirements Quality

• Are the requirements written in the user's language? Do the users think so?
  
• Does each requirement avoid conflicts with other requirements?
  
• Are acceptable trade-offs between competing attributes specified-for ex-ample, between robustness and correctness?
  
• Do the requirements avoid specifying the design?
  
• Are the requirements at a fairly consistent level of detail? Should any re-quirement be specified in more detail?
  
• Should any requirement be specified in less detail?
  
• Are the requirements clear enough to be turned over to an independent group for construction and still be understood?
  
• Is each item relevant to the problem and its solution? Can each item be traced to its origin in the problem environment?
  
• Is each requirement testable? Will it be possible for independent testing to determine whether each requirement has been satisfied?
  
• Are all possible changes to the requirements specified, including the likeli-hood of each change?

Requirements Completeness

• Where information isn't available before development begins, are the areas of incompleteness specified?
  Are the requirements complete in the sense that if the product satisfies every requirement, it will be acceptable?
  
• Are you comfortable with all the requirements? Have you eliminated re-quirements that are impossible to implement and included just to appease your customer or your boss?