CS 130: Software Engineering, Spring 2009: Final Project Document

Your final submission for the project should contain the following.

• The latest versions of your requirements/specification and design documents.
• An overview document that talks about the following points.
  • What have you accomplished? [Think of this as a "Release Note" for your software, describing the implemented functionality. If your final software differs from your requirement statements, also mention features that you did not implement, but which you would if you had more time.]
  • How much did you have to change the specifications? How adequate was the design? How accurate was the planning?
  • A list of "Known Issues" if any. [Don't list here features you have not implemented, but bugs and limitations in your system.]
  • If you were to start again, what would you do differently? [Were there team- and organization-related problems? How do you think you could solve them? Were there particular software engineering practices you would (or would not) recommend?] (You can limit the discussion to one or two paragraphs.)
  • What were the main (two or three, at most) lessons learnt in the project? [These could be general software engineering insights, or more specific lessons about your problem domain.] (You can limit the discussion to one paragraph each.)