TechnicalReportWriting-ECESeniorDesign.ppt

* We will focus on how to write a technical report. A) Project statement Project specifications: Describe the problem, describe the product (solution), why people want to use it, propose a timeline including designing the system, writing the proposal, and writing the report. Include a paragraph justifying that timeline (why are the tasks in that order, which are major and which are minor). In real-life system designs are under-specified, and it is your job to complete the specification in a sensible way given the overall requirements of the project. In practice, the specifications often need some adjustment as the design is fleshed out. B) The design proposal should be a concise summary of your overall system design. A design proposal is typically used to propose a particular solution to a problem. It explains how the author’s design works, demonstrates that the design meets all the requirements, and if necessary shows how the author’s design is superior to others. As in a professional environment we ask you to clearly lay out the problem, then match your solution to that problem description. You should be able to characterize your proposed system at a high level and describe your proposed implementation and how it will meet requirements. Use technical language as appropriate, but write for an audience outside your specific area. Title Overview presents the problem and your solution. Explain the problem to be solved by your design. Summarize your proposed solution, including your overall design approach. Specify how your design solves the problem and meets requirements. Design description gives a fuller presentation of your design, demonstrating to your reader that your design will work and will solve the problem. Uses some hierarchy (subsections, logical groupings of material) and briefly introduces each subsection. Organizes and introduces implementation by task or function, not by I/O. Describes the design’s interface. Specifies your plan for implementa