Descriptive Title of Project

Transcription

1 Descriptive Title of Project ECE4007 Senior Design Final Project Report Section L03, Antigravity Team Project Advisor, Dr. Whit Smith Aaron Chang, Team Leader Susan Johnson Jim Grabowski Submitted May 5, 2010

2 Table of Contents Executive Summary...ii 1. Introduction Objective...xx 1.2 Motivation...xx 2. Project Description and Goals...xx 3. Technical Specification...xx 4. Design Approach and Details 4.1 Design Details...xx 4.2 Codes and Standards...xx 5. Schedule, Tasks, and Milestones...xx 6. Results and Acceptance Testing...xx 7. Budget and Cost Analysis...xx 8. Conclusions and Future Work...xx 9. References...xx Appendix A...xx Appendix B...xx Your Team Name (ECE4007Lxx) ii

3 Executive Summary This section should explain the basic idea of your project, why it was done, the current status (project outcome), and recommended additional work. It should be written at a high enough level so that it can be understood by non-technical people (i.e., management). This section should be words in length, double-spaced. Your Team Name (ECE4007Lxx) iii

4 Descriptive Title of Project The primary purpose of the final written report is to document all aspects of your project so that it is clear (1) why it was done, (2) what was done, and (3) what still needs to be done. The emphasis should be on the technical aspects, but schedule and financial aspects also must be covered. These sections should be expansions of the material in your earlier proposal written report. However, you should not just copy sections from this earlier report every section must be updated appropriately. Note that the entire report should be double spaced. 1. Introduction The Introduction should be 2-3 sentences explicitly stating that team X spent Y amount of funding to develop Z. 1.1 Objective Describe what your team actually built. Put it in the context of the big picture. For example, explain if your project is a subsystem of a larger system or product, or if you plan to concentrate on a particular aspect of your project. Identify the customer for your project. 1.2 Motivation Why did you do this project? Is it new or a continuation of a previous project? Who will use the product? Does it improve upon an existing product? Does it offer a more cost effective alternative than an existing product or solution? Be sure to cite references for all relevant information. Your Team Name (ECE4007Lxx) 1

5 2. Project Description and Goals Give a clear, technically detailed description of specifically what was designed and prototyped by your group. Compare/present any modifications of the design that occurred between the proposal and the final demo (proposed vs. actual). State the goals that were met. The goals are such things as what the final product actually did, the cost for the product, and the targeted user. You should elaborate as to how well what you have done addresses these features; your project may only address a subset of what an eventual product would require. If you had to scale down your design, perhaps due to schedule or budget constraints, you should clearly state why it had to be scaled down but how you would extend or scale up your design to meet the original target goals. There may be some overlap with information presented in previous sections, but the focus of this section should be a bullet list of product features with accompanying discussion. 3. Technical Specifications This section should cover both the target technical specifications of the project or product, and the actual technical specifications of what you have implemented. The emphasis is not how it was implemented. Include qualitative and quantitative operational, performance, interface, physical and environmental specifications that apply to your project. Do not add additional specifications which are not required for your design. The specifications should be in tabular form with separate columns for the desired and actual specifications; there should be an accompanying discussion. This section is a Your Team Name (ECE4007Lxx) 2

6 critical part of your final report because the specifications capture the critical performance aspects of your project. 4. Design Approach and Details 4.1 Design Details This section contains the technical details of what was actually designed and built. This section should be detailed enough that someone else (perhaps another 4007 team) can build upon what you have done and take it to the next step. This section can refer to additional documentation that may be in the appendices or posted on your web site. This section should include the details of the design. Identify any parts of existing products or software or previous projects that have been used. Effective use of block diagrams, flow charts, schematics, interface diagrams, etc. is essential. If there is a Graphical User Interface (GUI), show what the screens look like and what information is displayed. Include any parts of existing products or software or previous projects that were used. Clearly indicate design aspects that were implemented as part of your project as well as any aspects that were designed but not implemented. 4.2 Codes and Standards What are the most significant codes and standards that apply to your project? How did they affect your design decisions? Cite references. Your Team Name (ECE4007Lxx) 3

7 5. Schedule, Tasks, and Milestones Show specific tasks (building blocks) of the project and the time line (schedule) for accomplishing these building blocks or milestones. Indicate how these tasks were divided up and who was assigned what tasks. Provide an overall project time line in the form of a Gantt chart with tasks, milestones, and critical paths shown. Note that most of the information in this section should be organized in the form of a Gantt chart and should not include long paragraphs of information. 6. Results and Acceptance Testing This is a very important section of your final report because it describes how your specifications are actually verified (acceptance testing). Describe specifically how you tested your design and present the results (quantify your results!). What was demonstrated and how did the prototype perform? How did the demo validate the project specifications? What specifications clearly were not met? Figures and diagrams of the demo along with written instructions and examples from the demo should be included. Explain if any additional tests are planned after submission of this report. 7. Budget and Cost Analysis Include a table that shows a breakdown of the cost of the project in terms of parts (hardware/software). State the original budget (include sponsored funds) and account for all expenditures. 8. Conclusions and Future Work Briefly summarize the current status of your project and then describe any future work that is needed to complete or optimize the design. What should be changed and why? What would you now do Your Team Name (ECE4007Lxx) 4

8 differently and why? In some ways this is the most important section of your report. Evaluate your initial goals and objectives and compare them to what was actually achieved. It may be that you have discovered a much better way to do this project now; if so, indicate that with a justification of why the unused approach is better. What recommendations do you have for future versions of the project? Is this product ready for production now or should another prototype cycle be initiated? Write this section with future 4007 students in mind who may continue your project. What additional work do you recommend? Consider a bullet list of future work. Be sure that your recommendations are technical and specific. 9. References Include a list of references for all items cited in this report. Use IEEE style format. You should include references for background information, similar products or projects, items you intend to purchased, cost information, and any other information that you have found and used for your project. You may have additional items not specifically referenced but which you consulted. If you do, put these in a separate section called BIBLIOGRAPHY in the form of an unnumbered list. Appendix Include material that is needed to understand your report but is too lengthy to incorporate into the body of the report. Extremely lengthy information (e.g., software listings) should be posted to your project website. Since one of the main purposes of the final report is to enable another group to continue your work, be sure to include all technical details. Your Team Name (ECE4007Lxx) 5