Report Guidelines ENGR 446
Report Guidelines ENGR 446
Report Guidelines ENGR 446
Faculty of Engineering
Summer 2015 ENGR 446 Report
Letter of Transmittal
University of Victoria
Faculty of Engineering
Re: ENGR 446 Report
May 1, 2015
Dear Student:
Welcome to ENGR 446. As per the University Calendar this 1.0 unit course includes a
major technical report demonstrating written communication and analytical skills. To
assist in writing this report and ultimately successfully completing the course the
enclosed report guidelines has been provided. Please review carefully.
Important Dates are summarized below:
Friday, May 15 4:30PM
Friday, June 12 4:30PM
Friday, July 10 4:30PM
Friday, July 31 4:30PM
We look forward to working with you on this course this term. Should you have any
questions please do not hesitate to contact the undersigned.
Regards,
Robin Ley
Co-op Coordinator & ENGR 446 Instructor
Jeffrey Martin
Co-op Assistant & ENGR 446 TA
Table of Contents
Table of Contents ....................................................................................................................... i
1.0 Introduction ........................................................................................................................ 1
2.0 Choosing a Topic ................................................................................................................ 1
3.0 Work Term Report Format ............................................................................................ 2
3.1 Title Page ........................................................................................................................................ 3
3.2 Letter of Transmittal .................................................................................................................. 3
3.3 Table of Contents and the List of Tables and Figures ..................................................... 4
3.4 Summary / Abstract ................................................................................................................... 4
3.5 Introduction .................................................................................................................................. 4
3.6 Discussion ...................................................................................................................................... 5
3.7 Conclusions .................................................................................................................................... 5
3.8 Recommendations ...................................................................................................................... 5
3.9 List of References ........................................................................................................................ 5
3.10 Glossary and List of Symbols ................................................................................................ 6
3.11 Appendices .................................................................................................................................. 6
1.0 Introduction
A major objective of the report is to successfully communicate technical ideas.
The entire report should normally be approximately 3,000 words in length, that is
approximately 12-15 pages of double-spaced text in 12 point font, on standard letter size
paper with margins not less than one inch.
The audience for your report will be your marker, who will be an engineer or computer
scientist. Write your report at a technical level that is understandable to your audience,
i.e. a reader who has an engineering background but who is not familiar with your work.
Your audience may probably not be familiar with the acronyms and local jargon. Make
sure that you define all acronyms and terms. A glossary placed at the beginning of your
report can assist the reader without hampering the readability of your report.
Write your report in a formal style, avoiding usage of the first person at all times.
Sentences such as "I machined five of these cylinders on the lathe" should be expressed
as "Five of these cylinders were machined on the lathe".
Writing style, spelling, punctuation and the report format will constitute 30% of your
marks. If you feel you need information on writing style, read one of the recommended
texts listed in the List of References at the end of the guidelines. If the report is not
confidential it is further suggested that you have someone peer review or proof read your
work prior to submitting.
The technical report is an engineering report. It is more than just a technical description
or a how to manual. It outlines how technical information was applied to solve an
engineering problem. The problem may be one that you worked on directly or assisted
with. Choosing a topic and developing the report content can be the most difficult part of
writing the report.
The following section will deal with developing a report topic. The rest of the guidelines
will describe the report format.
An example of a topic could be the adoption of a new CAD system. Rather than simply
including of unconnected information about the system, an issue could be why the change
is needed. The introduction would include enough information to allow the reader to
understand existing problems (e.g.. how the original drawing system works, difficulties
when trying to update/access drawings). The requirements for the new system could then
be introduced (e.g.. cost savings, speed, ease of use), then a discussion on which system
was chosen and why it was chosen would follow. If many options are considered evaluate
the advantages/disadvantages of the options using a defined criteria. Your conclusions
could be that the best system was chosen (based on cost, ease of use, speed, availability,
etc.) and you could recommend ways to overcome some of the compromises made (e.g..
purchasing a laser plotter at a later date to reduce up front costs). By having an issue, the
report will follow a logical flow and assist the reader to understand the issue.
Where possible include numbers and reference material to support your statements. For
example, stating that "adding a colour printer is not feasible due to costs," is not as
convincing as including a table of price quotes from potential suppliers.
Submit your work report topic to the ENGR 446 CourseSpace by the due date.
3.5 Introduction
The introduction:
provides sufficient background information for the reader to understand the rest of
the report;
clearly defines the engineering problem;
introduces the subject to be discussed;
indicates why the subject is important;
outlines the content of the rest of the report; and,
contains sufficient background information for the reader to understand the rest of
the report.
Introductions should never be longer than the discussion. If a significant amount of
background information is required, some of the material may be included as appendices.
The introductory material may be presented in several sections to cover the scope of the
report as well as provide the necessary background information.
3.6 Discussion
The discussion is the foundation of a report. It presents evidence in the form of
referenced facts, data, test results, calculations, and analysis upon which the conclusions
are based. A well-written discussion flows logically from concept to concept to lead the
reader to the appropriate conclusions. If different solutions are being evaluated,
advantages/disadvantages of each should be discussed. The criteria in which each option
is evaluated should be defined.
The discussion may contain several sections if several concepts are presented. Identify
any limitations of assumptions made to compete your analysis.
For information on the format of tables and figures, refer to section 4.4.
3.7 Conclusions
Conclusions are the results derived from the evidence provided in the discussion. No new
material is presented in the conclusion.
When presenting more than one conclusion, state the main conclusion first, followed by
the others in the order of decreasing importance to ensure the maximum impact on the
reader. Reinforce any limitations or assumptions that impact the conclusions.
3.8 Recommendations
Recommendations are an outline of what further work needs to be done based solidly on
the information you previously presented in the report. They have the greatest impact
when written using action verbs. Again, do not introduce new material or concepts here.
might be tables or figures from other sources, equations that you did not derive, technical
specifications or facts used to support your claims.
The IEEE format is the recommended format and is described in section 4.5
3.11 Appendices
Any data supplementary to the main ideas of the report may be placed in an appendix.
The information may be a description of the processes involved, analytical proceedings,
example calculations, computer printouts, technical specifications, or excerpts from other
reports. Any type of information may be placed in an appendix if it is relevant, provided
it is referred to in the main report.
An appendix refers to one set of information. If several sets of information are to be
included, several appendices may be used. Appendices may be referred to by letter
(Appendix A, B, etc.) or by number ( Appendix I, II, III or 1, 2, 3, etc. ).
Page numbers in appendices are hyphenated, eg. A-1, B-12, etc. In the Table of Contents
appendices are listed at the bottom with no page reference to avoid redundancy, since the
first page of appendix A would be A-1, and the first page of appendix B would be B-1,
etc.
1.
2.
2.1
2.1.1
3.
3.1
4.3 Headings
Every section in the report has a heading. A heading briefly describes the section that
follows and is most often followed by a paragraph rather than another heading. Section
and sub-section headings are used in the Table of Contents to assist the reader in locating
specific material in the report.
4.4 Capitalization
When writing reports, cover letters and resumes, try to follow the accepted rules of
capitalization. The two most relevant rules are:
This information was adapted from The Elements of Technical Writing, Gary Blake and
Robert W. Bly, MacMillan, pages 59-60.
conference proceedings [6], a manual- corporate author [7], a document published on the
web [8].
For a web article, give the author, title, type of medium (enclosed in brackets), volume
and issue number (if on-line journal), page number (if relevant or given), and the year
and the month of publication (in parentheses). Then give the full internet address or the
name of the online service provider prefaced by "Available at ". If not an on-line journal,
also put [cited year month day] before "Available at".
Cited References:
[1] J.A. Smith, An Introduction to Engineering , New York: Doubleday, 1981.
[2] A. B. Brown, P. D. Adams and J. A. Smith, "Improved procedure for error
detection," Can. J. of Elec. Engineers, Vol. 9, pp. 545-588, Nov. 1979.
[3] J. A. Smith,"A preliminary analysis of internal waves in the Strait of Georgia,"
UVic Electrical Engineering Report 84-3, 5 pp., 1984.
[4] H. Rosenblum, private communication, 1988.
[5] Phoenix Group,"Flight Simulator Study Results," Phys. Rev. Lett., Vol. 26, p.
1231, 1985.
[6] B. A. Trubnikov and V. S. Kudryartsev,"Plasma radiation in a magnetic field," in
Proc. 2ns U. N. Cong. Peaceful uses of Atomic Energy (Geneva), Vol. 31, p. 93, 1958
[7] IBM ASTAP Program Reference Manual, IBM Corp., 1973.
[8] A. Harnack and G. Kleppinger, "Beyond the MLA Handbook: Documenting
Electronic Sources on the Internet." Kairos, [Online serial] 1 (2), (1996 Sum), Available
at: http://english.ttu.edu.kairos/1.2/
Figure 2. Reference listing of various documents.
Note that each listing includes:
the name(s) of the author(s);
the title of the document;
For articles in journals, the title of the article is included in quotations;
For books, the publisher's name and location, and the year the book was
printed;
For articles, the name of the journal, the volume number and the date of
issue; and,
For reports, the report number, the name and location of the issuer and the
date of issue and the page number, when applicable.
When citing a reference within the report, the corresponding reference number may be
included in square brackets:
* at the end of a sentence just before the period, eg. [2].
* after figure and title labels, eg. Figure 1: Network Design [3].
* after the appendix title if the entire appendix is copied from another source, eg.
Appendix A [4].
* at the right hand margin beside a mathematical equation.
In the list of references, list the cited references in the same order as they are referred to
in your report. The reference numbers appear in square brackets at the left-hand margin.
General References are listed separately in alphabetical order.
Refer to Figure 3, below, for the overall format of the List of References.
Cited References:
[1] J. A. Smith,"A preliminary analysis of internal waves in the Strait of Georgia,"
UVic Electrical Engineering Report 84-3, 5pp., 1984.
[2] H. Rosenblum, private communication, 1988.
[3] Phoenix Group, "Flight Simulator Study Results," Phys. Rev. Lett., Vol. 26, p.
1231, 1985.
General References:
Brown, A. B., P. D. Adams and J.A. Smith, "Improved procedure for error detection,"
Can. J. of Elec. Engineers, Vol. 9, pp. 545-588, Nov. 1979.
Smith, J. A., An Introduction to Engineering. New York: Doubleday, 1981.
Figure 3. Example of the IEEE format
5. Closing remarks
The above guidelines are a condensed version of the material covered in the books listed
in the bibliography. Refer to the recommended texts for more detail. If you have any
further questions or comments, contact a coordinator at the Engineering Co-op Office ph.
(250) 472-5800.
11