User Requirements
This document is the drive for project documentation and individual system specifications. It doesn't have to be lengthy, but it should address the whole project.
User requirements constitute our guide to what you want. This document, which can be jointly prepared by QPS and the Customer, summarizes and formalizes the preliminary discussions and preliminary specifications such that both parties are clear about the goals and objectives. It will serve both companies best if the user requirements describe the end game, but do not constrain the path. This document should lay out the project from the user's perspective. It can start with a description and justification of the project and progress to specific goals.
" process methods
" document requirements
" regulatory considerations
" operational detail
" equipment
" space planning
" maintenance
Upon customer approval, the user requirements document is subject to change control. Authorized individuals at QPS and the customer company must certify changes to the project, since these would probably change the project budget.
The user requirements will be the guiding document for the project. Care and thought put in "up front" will result in satisfaction when the job is complete. If you aren't clear about what you want, you will most likely get what someone else wants.
|
