user requirements

• Do not write down a proposed solution.
• Think about how to demonstrate the requirement has been met, and write that down, too.
• Avoid jargon - either technical or business. Define any such terms clearly.

Also bear in mind the uses to which the user requirements will be put. This is likely to include one or more of the following (and potentially others):

• A feasibility study, evaluating various solutions.
• Estimates for the delivery of the chosen solution.
• Development of a user acceptance test suite.