Include the name of the document's author, author's telephone and email address.
Contributors:
List contributors to this document, and the nature of
their contributions.
Primary Contact:
All questions and comments about the project should
be addressed to the primary contact. It will be the responsibility of
the primary contact to answer or direct the questions or comments to the
appropriate parties.
The primary contact is usually the Project Leader. Include email link.
Distribution:
List the mailing list, Usenet group, web address, or
other method of intended distribution.
REVISION HISTORY
Date of Revision
Revised By
Description of Revision
Affected Modules
QUALITY PLANNING
Development Methodology
For the purposes of this project, we are using a simplified Project Life
Cycle, the details of which can be found at www.kuhnllc.com.
Change Control
Audit Plan
BUSINESS REQUIREMENTS
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.
WORK PLAN
List Major Milestones with an estimated schedule. You should link to an external document that is maintained under revision control.
