[Robotics/Bridge] Module: Final Report

ENGR 102 – Winter 2015 - 2016

Engineering Design Lab II

Lab Section: / XXX / Date Submitted: / MONTH DD, YYYY
Group Number: / YY
Section Faculty: / Faculty name / Section Fellows: / Fellow name 1
Group Members: / Group member 1 / Group member 2
Group member 3

Note that all red text represents placeholder information! There should be no red text in your final submission! Be sure to maintain the formatting structure in this document when submitting. Specifically:

·  This report should be no more than 5 pages in length (not including this first (cover) page – which should include your abstract, and also not including your references), but including all figures and tables.

·  The report should be written in the third-person passive voice and in past tense.

·  The final submission will be uploaded to the corresponding assignment in your lab section BbLearn page. Submissions must be in PDF format, and follow the proper naming convention (replacing “xxx” and “yy” with your group’s lab section and group number respectively). Update the information in the header of this template with your group and section numbers as well.

·  Final submissions should be no more than 3 megabytes in size. Large file sizes usually have to do with large, uncompressed images in your submission. In Office 2010 and later, you can compress a figure by double-clicking it and selecting Compress Pictures in the top pane. Make sure to choose ‘All images in document’ to compress everything. See the link here for more information.

Abstract

Place your abstract on the title page. Remember, the abstract should be no more than 300 words in length and it should not go past this page. The goal of the abstract is to summarize for your audience the content and major highlights of your report. It is best written after everything else in the report has been completed. See the report-writing instructions for more information.

ENGR 102, Winter 2015 - 2016 Section XXX, Group YY

Structuring your Report

Unlike previous report templates, this one will not give a detailed outline of required sections. It is up to your group to determine how best to structure your report. As a general guide, most reports and technical papers can be written as follows.

·  Abstract – Brief summary of entire paper

·  Introduction/Background section – Motivation for the work that is being done. Why is it important? What are the technical challenges, objectives, and constraints?

·  Technical content – Several sections containing the technical activities of the project, including experimental data and findings. This should make up the majority of your report and should be broken into multiple sections and subsections in order to organize the material. All content related to the design process for your bridge or robot must be fully documented and included in this section!

·  Conclusion – Describes how your design performed. Include a discussion of lessons learned and future improvements that could be made.

Useful information for Report Writing

This template is only a starting point. When writing your report, you are expected to think about structure, incorporate visuals when appropriate, and cite relevant materials. This section provides information that should be helpful in writing your design proposal and final report.

Using Subsections

Use subsection headings liberally to divide your report into logically distinct pieces. This helps users quickly navigate to sections of interest. This template has Heading 1, Heading 2, and Heading 3 formats defined. These should be used for section, subsection, and sub-subsection headings, respectively.

Referencing Figures, Tables, and Other Content

All figures and tables must be referred to in the text. It is not sufficient to simply include the item without any explanation in the body of the document. For example “Figure 1 shows Ironman in front of menacing storm clouds. The storm doesn’t worry Ironman though. His armor will protect him.” Captions should be kept brief. Detailed explanation of the figure belongs in the body of the report.

Figure 1: A brief description of the figure, placed below the figure and centered.

Citing Other Work

The results presented in a technical paper are generally built upon or influenced by other work. Any citations to other work must follow the IEEE citation guidelines (http://www.ieee.org/documents/ieeecitationref.pdf). Two examples of references are given in the “References” section at the end of this document. Anything appearing in the References section must be cited in the body of the document. The following paragraph shows how to cite a reference in the body of a document.

“As early as the 1950s, film-makers had recognized the potential of electronic cameras in film-making [1]. Prior to the availability of digital cameras, several research groups had developed drop-in devices that would essentially convert analog cameras to a digital format [2].”

·  You are required to obtain a minimum of two references for the Final Report. For this report, you are required to cite at least one reference from the McGraw Hill AccessScience online encyclopedia (you can pull both citations from this as well).

o  Access here: http://www.library.drexel.edu/cgi-bin/r.cgi?url=http://accessscience.com

o  For the Robotics module, start by searching for the term ‘Robotics’

o  For the Bridge module, start by searching for the term ‘Truss’

·  References should be numbered as they appear in the document, not by date or author’s name.

·  For this course, you are not permitted to cite webpages.

·  You should not cite the design proposal or lecture slides. You should not copy figures from these sources either.

References

[1]  Collins, Norman; Macnamara, T.C., "The electronic camera in film-making," Electrical Engineers, Journal of the Institution of , vol.1953, no.2, pp.90,, February 1953

[2]  Hurwitz, J.; Panaghiston, M.J.; Findlater, K.M.; Henderson, R.K.; Bailey, T.E.R.; Holmes, A.J.; Paisley, B., "A 35 mm film format CMOS image sensor for camera-back applications," Solid-State Circuits Conference, 2002. Digest of Technical Papers. ISSCC. 2002 IEEE International , vol.1, no., pp.48,443 vol.1, 7-7 Feb. 2002

Page 1