Final Team Report

How to Submit, and Deadline   

  1. Submit your Final Report in hardcopy into my mailbox or in my office (503A).
  2. Deadline: August 9 (Monday), 2004, 5:00 pm.

------------------------

 

The final team report should include at least the following.

 

  1. Cover sheet
  2. Table of contents
  3. Introduction
    1. Brief description of need/purpose of the systems
    2. List of stakeholders
    3. Basic overview of functions provided by the systems
  4. Process followed
  5. Basic discussion on approach, methodologies used, management approach, tools, techniques, etc.
  6. Requirements change discussion. A paragraph or two describing how the requirements change affected your design.
  7. Abundant design rationale.
  8. Implementation discussion. A one-page discussion of how your implementation went. What went well? What went badly? What should you have spent more time designing? etc.
  9. Review and meeting process
  10. Team member responsibilities
  11. Major problems encountered
  12. What was learnt? Describe how well cooperative learning occurred in your team
  13. Latest changes based on the heuristic evaluation results. List the problems that were not solved and your arguments why so.
  14. Describe any conflicts and how they were resolved.
  15. Specify what is left to be done.
  16. Source code analysis results and other measurable results. You can use Source Code Metrics tools available free on the Web to report interesting metrics such as the NLOC, number of member functions/class, coupling between objects, etc. Include your conclusions (0.5-1 page).

 

It is important that your report be organized and has only one editor even though it will contain contributions from all the team members. The responsibility of the editor include turning in the final document, setting deadlines for individual submissions, and incorporating individual submissions into a single coherent and complete document.