The first section should identify the requirements in detail. This should be based on your project description, but you if you have recognized a need to change the requirements you can do so here. The section should start by stating the goal, then one or more use scenarios should be described, and then the specific requirements should be listed. The specific requirements section should be organized in a manner that facilitates tracablity, giving each requirement a unique code (e.g., A, B, ...). All requirements must be grounded in the user experience; implementation details do not belong in the requirements section. Your project will be graded based in part on its ability to meet the requirements stated in this section.
The second section should describe the implementation details. The section should begin with a description of the tools that you are using and an overview of your strategy for using those tools to create the user experience. The implementation of front end (display and control), back end (storage and access), and content (information sources and preprocessing) should then be described in turn. The second should conclude with a list of limitations on the ability to meet the reqirements that result from implementation considerations.
The third and final section should describe the ways in which you plan to test your system. This section will not be graded, but it will give you an opportunity to think strategically about the role of testing during system development, and it is possible that obvious gaps in your testing strategy may give me ideas on some things that I shuld be on the lookout for when I try out the results of your project.