1.2.2 Written Proposals

Description: a formal proposal written as if it were to be reviewed by a prospective client who is considering financing your project. It should contain a statement regarding the objectives of the project and their value to the segment of the technical community to which the project is addressed. The proposal should demonstrate your understanding of the issues and present the approach you are proposing to take to achieve stated objectives. The proposal should include sufficient detail about the critical elements of the project to afford your primary audience the opportunity for offering constructive criticism.

Two kinds of proposals:

Solicited: You respond to a published Notice of Program Interest (NPI) or a Request for Proposals (RFP). You must demonstrate understanding of the need expressed by the client

Unsolicited: You declare that a need exists. Your proposal must demonstrate that the need exists and is important to the client or funding agency. Furthermore, you must demonstrate that your work fits within context of previous work in this area.

Structure:

Introduction:
1. Cover page
2. Introduction: statement of motivating problem; identify key technical issues (need); statement of objective.
Body:
1. Overview of technical approach and appropriate theoretical background with references to applicable theory, analytical models, hypotheses, or previous pertinent work
2. Experimental methods and test design
3. Data acquisition: Description of data that will be taken
4. Methods of data analysis: how data may answer to the motivating need expressed earlier.
End:
1. Time schedule (Gantt chart): Task v. time (in weekly increments for both semesters; also indicate important milestones)
2. Required facilities and resources (including a proposed budget).

Show whole document examples:

Castro, Zachira Active Control of a Diffuser
London, Adam Method of Improving Space Simulation In a One-g Natatorium

ebarrett@mit.edu

schiu@mit.edu