"Get the facts, or the facts will get you. And when you get them, get them right, or they will get you wrong. "
-- Dr. Thomas Fuller (1654 - 1734),

Management Tips

{Project Name}

Business Requirements

Remove italicized comments within this template from the final document

Include the name of the document's author, author's telephone and email address.

List contributors to this document, and the nature of their contributions.

The primary contact is usually the Project Leader. Include email link.

List the mailing list, Usenet group, web address, or other method of intended distribution.

Date of Revision	Revised By	Description of Revision	Affected Modules

These are the user requirements. The enumerated requirements are as accepted and extracted from the Business Proposal.
Add sub-headings as appropriate.
Number each requirement for future reference.
Write requirements in a manner that can be objectively tested. However, do not avoid writing a requirement simply because it's not objective.
Requirements may be business and/or technical in nature -- they should only be technical when the user has mandated a particular technical solution. Remember that this is a list of the what requirements should be met, not how.
User acceptance is tied to the requirements.

List Major Milestones with an estimated schedule. You should link to an external document that is maintained under revision control.

{add additional appendices as required}