CSE 444

Spring 1999

Project Planning and Documentation

4/19/1999

Eventually, your project should develop and turn in all of the following material.   Some of these might be short and perfunctory, others might be more elaborate.   Many of these can be started immediately, and then kept up to date.  The instructor and TAs will ask for a current copy periodically. It's the project leader's responsibility to maintain the plan (of course, that can be delegated!)

• Summary of project goals.  One paragraph.  Ideally, it should be comprehensible to someone non-technical.
• Top-level description of completed system.
• Contacts: everyone in your group, plus any sponsor or client people you need to contact
• Client overview.  Description of client organization and client/sponsor/end users.   Focus on the organization and the types of people involved, rather than specific individuals.
• Log or diary of contacts with sponsors/clients.  Make a note every time you contact them, and especially note in-person meetings: when, where, who.
• Platform requirements.  Include both hardware and software.  Distinguish between where you will develop, and where the client will ultimately use/host the system.
• Schedule of milestones
• Use and requirements overview.
• Data model (E/R diagram)
• Database design (relational schema)
• System design spec.  Something that describes what you're doing: what functions/programs need to be written, what each one does, where each one fits into the system, etc.
• Test plan.
• Program listings and other artifacts.
• Demonstration scenario or plan
• Turn-over plan.
• Final report.