Finally, please make your documents professional. Part of your grade on the documents will depend on the appearance, organization and attention to clear writing in your documents.
Requirements Document for the XYZZ project
Your names here together with email addresses.
Include, in your own words, the purpose of a requirements document.
This should be a list of each change to the document together with the date the change was made and the reason for the change (i.e., respond to client's or reviewer's comments). The first entry should be the date on which the document was first turned in to me.
I use \LaTeX for much of my writing, and would be happy to give an hour's lesson in its use. I'm sure that any word processor you use will have some provision for table of contents (though I've never learned how to do it in MS Word, I'm afraid).
Brief description of the problem this system solves, and how it will solve the problem. For further details on this (and the following sections), please refer to the generic document outline on page118.
Definitions of technical terms. Remember that you are writing for both a technical and a non-technical audience.
Note: The requirements in sections 3 and 5 should be divided into sections on functional requirements and non-runctional requirements
Assumptions made in determining how the system will operate and
how it will change in the future.