thezip, that's a nice list. I would add requirements to explicitly deal with persistent production data and data structures such as procedures to convert/upgrade data and plans and procedures to revert back to the original data structures and data when needed. The impact of code on database data cannot be underestimated.
In addition it makes sense to add an automated install procedure to the requirements list. Not so much for convenience but most importantly to ensure that all installation steps will be executed as a formal pre-documented and logged sequence. this makes the process repeatable and fit for later analysis should that be needed.