Student Originated Software 1997-1998 Fall Quarter
		A Software Engineering Course at The Evergreen State College

Student Originated Software System Development Plan Case Study Assignment Fall Quarter, 1997 Version 0.2 Last Revised: October 5, 1997 Due: October 14, 1997 Now that we've decided that we are going to proceed with this project we need to begin to specify how we're going to proceed. The purpose of this assignment is to produce a program plan that outlines the details of this. The system development plan is a coordinating instrument and it should be consulted and updated as necessary throughout the project. As with the Feasibility Study document, this document will necessarily be a preliminary document. Nevertheless it is almost never too early to begin to think about the specifics of allotting resources (including time, money, equipment) to objectives given the constraints (time primarily). Since this is preliminary it is important to note that it is subject to change. You don't want to arbitrarily or casually change it, however, as it represents a public formalization and agreement of how the team intends to successfully complete its tasks. The suggested contents of the software development plan are listed below. Feel free to modify these if you want. Change the order, add or delete sections if you think it's appropriate. This document should be fairly brief (1 - 4 pages). As before, it must be typed and list the names of all team members. It should also have a date and version number. Introduction A brief description of the system development plan. This part of this plan should discuss how this plan will be used throughout the course of the case study and the process by which the plan can be changed. Resources A summary of resources that will be deployed in order to develop the system. This should include a list of all personnel and what their responsibilities (both primary and secondary will be). It should also list the software and hardware resources that will be used. This section should also include (if applicable, of course) discussion of any new expenditures for training, hardware, software, consulting, etc. and a budget. Schedule A short description of major project milestone and a timeline that shows duration of each activity and due date of each deliverable. (You will want to consult the syllabus for some of the milestones and due dates.) Milestones should include software delivery dates (modules, user interface, final or phases delivery etc. as appropriate), testing periods, documentation delivery dates, code reviews, etc. Other Relevant Topics (if any)