CSE/ISE 308
Fall 2004
Stony Brook 		Software Engineering
Annie Liu
Final Project Report 		Handout R
Nov. 30, 2004
Due Dec. 9

Each group is asked to write a final report by organizing all your assignments together, writing a summary and a conclusion, and including the slides of your presentation. To get any credit, individuals must also write what he or she and others did for the project. Details of the requirements are explained below.

1. On the first page, write down your project title, group name, group members and their email addresses, and an URL for the group project containing all project related information.

2. Also on the first page, write a 200-word summary, summarizing the purpose, effort, result, and other highlights.

3. The main part of report should include description of the following items.

  1. project description (assignment 2, 1wk)
  2. project plan (assignment 3, 1wk)
  3. requirement elicitation (assignment 4, 1wk)
  4. requirement analysis (assignment 5, 1wk)
  5. system design (assignment 6, 1wk)
  6. object design (assignment 7, 1wk)
  7. coding and optimization (assignment 8, 2wks)
  8. testing (assignment 9, 1wk)
  9. delivery (assignment 10, 1wk)
  10. maintenance and improvement (2 wks)
  11. list of revisions and improvements to the assignments
For each of items 1-9, include your corresponding assignment revised and improved to the best you can; the requirements for each item are as specified for that assignment. For item 10, summarize what you did on the project during the last two weeks, in no more than one page; a paragraph could be sufficient if you did not need to do much. For item 11, list the revisions and improvements you did to each assignment and point out where each change is in the final report (e.g., for the coding part: (1) changed the number of lines of code written from 500 to 2000, in paragraph 2 on page 5; (2) added interesting optimizations, in section 7.4 on page 30).

4. Write a conclusion for your project: what you achieved and learned, what you did not finish and are for possible future work, and anything else that you feel worth mentioning. This should be about 800 words.

Throughout the report, you should emphasize how your group tried reuse, incremental and iterative development, and use of tools and achieved any good goals (e.g., reducing system cost, making system easy to use, increasing system performance, assuring system correctness). You may include additional description of these items separately after the conclusion, if you feel that you have really interesting things to say; for various issues that were not explicitly required or emphasized (e.g., comparing nontrivial features of your system with other known systems using say matrices, reducing software cost, increasing DB system performance, automating testing, providing multiple options for delivery, other ways of making your system easy to use), you will get extra credit proportional to the estimated effort.

5. Include slides from your project presentation; print 2 or more slides on one page, so long as they are readable.

An extra note: Check all your final code and documents into the CVS repository set up for this course.

6. Each member of the group is asked to sign the final report to get credit, and by signing it, s/he asserts that all stated in the report are true to the best of his or her knowledge. Put your signature next to your name on the first page.

7. Finally, all of you have experienced some good and/or bad aspects of team work in this course. I ask that each person individually write a summary of what he or she did for the group project and what he or she knows what others did for the group project. The amount of detail is up to you, but make sure that it is typed (so that it is readable), is not longer than one page, and is informative. For example, you could write that "I did the entire project", or "I made class diagrams with A, and B revised them; I wrote code for the class Account with B, and C suggested some changes; D and E said they reviewed the code but suggested no changes; I did testing with D while E watched; C and D prepared presentation slides; A and B reviewed the slides and suggested changes; ...".

Note this must be completely honest and must make any collaboration explicit. In particular, if you write "I did the entire project", it means that "no one else did it with me". If you write "I did so and so with A", it means "you and A both did, and no one else did". If you only watched others in your group doing it, then say so also.

If your group had problems and resolved them yourself (or could not resolve them), and you feel that it was a good learning experience, you may summarize it here also. Please feel free to summarize anything else not mentioned but you think is important and interesting to get from this course.

Handins

Each group is asked to hand in a printout in class. Each person is asked to hand in a printout of the last part in class.

Grading

This final project report, confirmed with your project demo at the end of the class, is worth 30% of the course grade. If you made extra effort to get extra credits, please make it explicit to receive appropriate credits.