Results Document
Your final report will include a results section. The purpose of this working document is to begin to gather those results. Information in this section will vary by project, but may include:
- list of features you did not have time to implement
- performance testing results
- summary of testing (e.g., browsers)
- results of usability tests (e.g., testing educational software with real students)
- future work (e.g., any ideas you may have for extensions)
- lessons learned
The documents below provides some examples from prior sessions:
Lessons and decisions should include specific details, and not be just general statements such as "we chose Java because we all know it." Fluffy statements like "We really learned a lot and were able to create a great product that will be really helpful to our client" are also not informative.
