Guide for Writing Project Proposals
Guide for Writing Project Proposals
This is a summary of how to write good, concise proposals for course projects. The focus of this summary is on programming or implementation projects, but the general ideas can be applied to most proposals. The recommended lengths of sections are given assuming a document length of 2 to 5 pages. Use appropriate scaling for longer proposal documents.
Sample Outline
The following is a sample outline for a project proposal. Note that all questions for a section may not apply to your proposal, and should be used as a general guide only.
1. Introduction (1 or 2 paragraphs)
1. Motivation Sentence
2. Summarize the problem (1 or 2 sentences)
3. Summarize the solution (1 or 2 sentences)
4. Describe format of rest of proposal (sections, etc.)
2. Motivation (1 to 3 paragraphs)
1. What is the history of the problem?
2. Why is this problem interesting?
3. When and why does the problem occur?
4. Is the problem already solved? What is done now?
5. Are there any similar systems or solutions to the one you propose? If so, reference and very briefly explain them.
6. Are there are possible improvements to current solutions?
3. Project Summary (1 paragraph)
1. What in general will this project achieve? (Do not delve into details or timelines.)
4. Project Details
1. Architecture and Environment (2-3 paragraphs + figures)
1. Describe the project environment (software, hardware, languages, organizations, etc.)
2. Diagrams and figures are useful here if appropriate.
3. What software, hardware, or tools will you use?
2. Implementation Issues and Challenges (2-3 paragraphs)
1. What will be the most difficult issues and challenges in the implementation?
2. How are you using or extending current tools/systems for your problem?
3. What makes your project unique?
3. Deliverables (3-5 paragraphs - point-form may be used for some of the description)
1. What will the project produce? (program, report, etc.)
This is a summary of how to write good, concise proposals for course projects. The focus of this summary is on programming or implementation projects, but the general ideas can be applied to most proposals. The recommended lengths of sections are given assuming a document length of 2 to 5 pages. Use appropriate scaling for longer proposal documents.
Sample Outline
The following is a sample outline for a project proposal. Note that all questions for a section may not apply to your proposal, and should be used as a general guide only.
1. Introduction (1 or 2 paragraphs)
1. Motivation Sentence
2. Summarize the problem (1 or 2 sentences)
3. Summarize the solution (1 or 2 sentences)
4. Describe format of rest of proposal (sections, etc.)
2. Motivation (1 to 3 paragraphs)
1. What is the history of the problem?
2. Why is this problem interesting?
3. When and why does the problem occur?
4. Is the problem already solved? What is done now?
5. Are there any similar systems or solutions to the one you propose? If so, reference and very briefly explain them.
6. Are there are possible improvements to current solutions?
3. Project Summary (1 paragraph)
1. What in general will this project achieve? (Do not delve into details or timelines.)
4. Project Details
1. Architecture and Environment (2-3 paragraphs + figures)
1. Describe the project environment (software, hardware, languages, organizations, etc.)
2. Diagrams and figures are useful here if appropriate.
3. What software, hardware, or tools will you use?
2. Implementation Issues and Challenges (2-3 paragraphs)
1. What will be the most difficult issues and challenges in the implementation?
2. How are you using or extending current tools/systems for your problem?
3. What makes your project unique?
3. Deliverables (3-5 paragraphs - point-form may be used for some of the description)
1. What will the project produce? (program, report, etc.)
References: 1. List references used to compile proposal and references that will be used for project (if already known).