The following is an outline for text of a project proposal. The recommended lengths of sections are given assuming a document length of approximately six pages. Note that all questions for a section may not apply to your proposal, and should be used as a general guide only.
- Introduction (1 or 2 paragraphs) o Motivation Sentence
o Summarize the problem (1 or 2 sentences) o Summarize the solution (1 or 2 sentences)
o Describe format of rest of proposal (sections, etc.)
- Background (1 to 3 paragraphs)
o What is the history of the problem? o Why is this problem interesting?
o When and why does the problem occur?
o Is the problem already solved? What is done now?
- Are there any similar systems or solutions to the one that is proposed? If so, reference and very briefly explain them.
- Are there are possible improvements to current solutions?
- Project Summary (1 paragraph)
- What in general will this project achieve? (Do not delve into details or timelines.)
- Project Details
- Project Scope and Elements (2-3 paragraphs + figures)
- Describe the overall project and then break it down into the steps or elements necessary to bring the project to fruition.
- Diagrams and figures are useful here, if appropriate.
- What software, hardware, or tools will be used?
- Implementation Issues and Challenges (2-3 paragraphs)
- What will be the most difficult issues and challenges in the implementation?
- Will any special facilities or equipment be needed in the execution of the project?
- Where will the project be constructed?
- Will any unique skills be required?
- Deliverables (3-5 paragraphs – point-form may be used for some of the description)
- What will the project produce? (prototype, model, program, report, etc.)
- Describe in relative detail the features of each of the project’s products.
- You may wish to separate deliverables into phases and indicate optional components given time.
- Emphasize what your project contributes or achieves!
- Timeline (1 paragraph – point-form is suitable)
- Provide an estimated timeline of project deliverables and important dates.
- Gantt Chart
- Budget (1 paragraph + list/table)
- What will be the cost to execute the project?
- What is the source of funding for the project?
- Are there outside sources of funding?
- Conclusion (1 paragraph)
- Summarize the project including the problem, motivation, and proposed solution, and re-state important (planned) contributions.
- List references used to compile proposal and references that will be used for project (if already known).
The EggBot project, according to the YouTube video from the reference, it is slow and shaky. We assume it was poorly designed so it ended up with shakiness. In addition, we think the slowness is a result of the programing.
Starting with this design, our idea is to create a solid design first and try to make it more accurate and nicely looked. However, we are thinking of using the same circuit and program that listed in the reference and see how it works. Then, we will see how to improve the efficiency of the program.
Proposal Writing and Format
The proposal is a relatively short document; thus, it will not be bound but will be stapled in the upper left corner. The cover will be the title page that is shown prior to this page.
Since the proposal will be stapled, rather than bound, use a one-inch margin at left, bottom and right. The first page of text should have a two-inch margin at the top. Use a one-inch top margin on all succeeding pages.
Use a 12-point font for the text. Times New Roman (an example is the title page), Calibri (an example is the body of this document), or a similar font is suitable. It should be reasonably plain and easy to read. The body of the text should be single-spaced, with double spacing between sections of the body and between paragraphs within a section.
This paragraph is an example of a second paragraph within a heading in the body of the report.
Preface pages are numbered with lower-case Roman numerals (i, ii, etc.), while the body of the text is numbered with Arabic numerals (1, 2, etc.). The first preface page (the title page in this case) should bear no page number. The body of the text should begin with “1” and all succeeding pages should be numbered consecutively to the end. Page numbers should be placed at the bottom center or bottom right.
Page | 1
A header or a single line of text is never left at the bottom of a page. A header must have some text with it, and the last paragraph on the page must always be at least two lines of text.
Figures and Tables
All figures and tables must bear an identification number and a title (e.g., Figure 1: 1936 Stout Scarab). The title of a figure is placed beneath the figure, while the title of a table is placed above the table. The figure or table should be placed in the report as soon as possible after its reference. An example of a streamlined vehicle is the 1936 Stout Scarab, which is shown in Figure 1.
Figure 1: 1936 Stout Scarab
Any figure or table included in the report must be referenced in the text of the report.
In the early to mid-60s, Detroit began to produce personal luxury vehicles, along the lines of the full-size Thunderbird. Pontiac’s entry into this field was the Grand Prix which was introduced in
1962 as a two-door hardtop (see Figure 2).
Page | 2
Figure 2: 1962 Pontiac Grand Prix
The Grand Prix was offered for the first and only time as a convertible in 1967. This model is shown in Figure 3. The productions numbers for the convertible were fairly low (see Table 1), making this a relatively rare car today.
Table 1: Production Numbers for 1967 Pontiac Grand Prix
1967 Pontiac Grand Prix
Body Style Production Number Coupe 37,125 Convertible 5,856 Total 42,981
Page | 3
Figure 3: 1967 Pontiac Grand Prix Convertible
Grammar and Spelling
The report is to be written in third person, thereby avoiding the use of “I” and “we”. Be sure to use available spelling and grammar checking features of the chosen software package to help eliminate errors. When done, be sure to proof read the entire report, as the grammar and spelling checkers will not catch all possible errors.
Page | 4