ICS 125:
Project in Software System Development

Fall Quarter 2003

DRAFT: Prospectus

As has been discussed in class, you have substantial flexibility in choosing the specific form for the content of your deliverables. Below is a list of items that should be included in your first deliverable, a project prospectus.

There is no need to select a manager and clerical support for this deliverable nor will you be doing performance appraisals at this point. Rather you should use this opportunity to brainstorm and get to know each other.

Due Date

As shown on the course web site.


One of your major tasks for the current period of time is developing an understanding of the various technologies and tasks concerned with your project. This includes the tools and techniques that you will use in accomplishing your task as well as the technologies that you will be extending, enhancing, or changing.

In this deliverable you should reflect your newly gained understanding by writing an introduction to your project that highlights its various important aspects. You should also include a description of activities done in support of developing understanding - like interviews with the customer, for example. (One of the best ways, of course, to gain an understanding of a piece of software is to interview the original developer.)

Technical Marketing Sheet

Include a one or two page technical marketing sheet (a bit more technical than a "sales brochure") suitable for describing your product to a technically literate outside audience. This document should be successful in reflecting that you really understand what problem is being solved and can articulate how your product will add value.

Project Plan

Use the outline below in presenting your project plan.

Prospectus Presentations/Reviews.

Each team must prepare a 15 minute presentation, after which we will allow up to 5 minutes of questions. Prepare your presentation appropriately. Your presentation should describe both your technical marketing and your project plan. Focus on the essential issues: the key technical goals, challenges, and risks. Don't spend air time on the obvious.