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

Student Originated Software Feasibility Study Case Study Assignment Fall Quarter, 1997 Version 0.2 Last Revised: September 27, 1997 Q & A: October 7, 1997 Due: October 9, 1997 "All projects are feasible," Roger Pressman points out, "given unlimited resources and infinite time!" Unfortunately, as we all know, this never occurs -- even here at Evergreen! Our first case study task is to produce a Feasibility Study that is governed by the real-world concerns and constraints that we are bound by. This document will focus on how likely we are to succeed given what we know and can assume about the project. Because there are many unknowns and because we've done very little analysis, this document will necessarily be a preliminary document. This is a good time to acknowledge the gaps in our knowledge and what we will be needing to find out in order to successfully complete the project. Therefore, when producing this document please note any relevant yet unresolved issues. Please also articulate any questions you have that need answering -- and how you plan to get them answered. The suggested contents of the Feasibility Study (from Pressman) 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 preliminary study can be fairly brief (2 - 5 pages). Introduction A brief discussion of the problem, the environment in which the system is to be implemented, and constraints that affect the project. Management Survey and Recommendations A summary of important findings and recommendations for further system development. In other words, what should be done? Alternatives A presentation of alternative solutions to the problem (if any); criteria that were used in selecting the final approach. System Description An abbreviated version of what the system will do. Ultimately the information will be contained in the System Specifications. Cost-Benefit Analysis An economic justification for the system. Minimally this includes a discussion of economic benefits (through reducing error, saving time or money, increasing sales, etc.) and costs (personnel, equipment, time, etc.). Ultimately this would be used to judge the economic feasibility including payback times under a variety of presumed circumstances. Evaluation of Technical Risk A presentation of technical feasibility. Can it be done given the technical constraints and resources? Legal Ramifications Other Project Specific Topics