Guidelines for Proposal Write Up and Presentation
Guideline for Proposal Write-up and Presentation
Heng Ji hengji@cs.qc.cuny.edu
1
Project Proposal Write-up
The proposal should be about 2-4 pages. The basic content can be as follows. 1.1 Executive Summary
An Executive Summary, which provides a brief (about two paragraphs) overview of the proposed project. This is probably the most important section of your proposal, because it provides a clearly defined problem and proposed solution procedure, and a description of the expected project deliverables. The Executive Summary is often the only section of your proposal that some readers will read; and must present all the relevant information as clearly and effectively as possible. It is often the last thing to be written. 1.2 Goal
The specific objectives of project. What are the defining features and benefits of this product? 1.3 Background and Motivation
What are the needs or problems that you are trying to address? Why do these needs (still) exist? Why are these problems worth solving? Who is the customer? Write 2-4 paragraphs. -What is the setting and history behind this project? -What is the problem to be addressed? -What are some current approaches to this problem? -Why is this problem worth solving or worth solving better? -How will this product be better than previous approaches?
1.4
System Architecture and Approach
This section identifies the approach that the team will use to meet the project objectives. You should explain here your principal tasks, their duration, their sequence and their particular purposes. Wherever possible, the methods and task to be performed should be outlined in logical sequence and explained in detail. Do not assume the reviewer will fill in the gaps in your logic. A common way of identifying project milestones and due dates is to use a graphic representation of the task relationships, such as a Gantt Chart (a bar chart showing timeliness for each principal task) or a PERT/CPM Chart (a network representation
Heng Ji hengji@cs.qc.cuny.edu
1
Project Proposal Write-up
The proposal should be about 2-4 pages. The basic content can be as follows. 1.1 Executive Summary
An Executive Summary, which provides a brief (about two paragraphs) overview of the proposed project. This is probably the most important section of your proposal, because it provides a clearly defined problem and proposed solution procedure, and a description of the expected project deliverables. The Executive Summary is often the only section of your proposal that some readers will read; and must present all the relevant information as clearly and effectively as possible. It is often the last thing to be written. 1.2 Goal
The specific objectives of project. What are the defining features and benefits of this product? 1.3 Background and Motivation
What are the needs or problems that you are trying to address? Why do these needs (still) exist? Why are these problems worth solving? Who is the customer? Write 2-4 paragraphs. -What is the setting and history behind this project? -What is the problem to be addressed? -What are some current approaches to this problem? -Why is this problem worth solving or worth solving better? -How will this product be better than previous approaches?
1.4
System Architecture and Approach
This section identifies the approach that the team will use to meet the project objectives. You should explain here your principal tasks, their duration, their sequence and their particular purposes. Wherever possible, the methods and task to be performed should be outlined in logical sequence and explained in detail. Do not assume the reviewer will fill in the gaps in your logic. A common way of identifying project milestones and due dates is to use a graphic representation of the task relationships, such as a Gantt Chart (a bar chart showing timeliness for each principal task) or a PERT/CPM Chart (a network representation