Scribd
Upload
41 views1 page

Technical Report Format

This document outlines the proper technical report format for EECS 563. It emphasizes that writing is an important skill for engineers and scientists, as work needs to be reported to receive credit. A good report has an introduction, narrative, and conclusion and is written for a specific audience. The report format specified includes a title page, abstract, table of contents, introduction, objectives, system overview, discussion of results, conclusions, references, and appendices. Brevity, clarity, and proofreading are stressed.

Uploaded by

Sagar G Reddy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
41 views1 page

Technical Report Format

This document outlines the proper technical report format for EECS 563. It emphasizes that writing is an important skill for engineers and scientists, as work needs to be reported to receive credit. A good report has an introduction, narrative, and conclusion and is written for a specific audience. The report format specified includes a title page, abstract, table of contents, introduction, objectives, system overview, discussion of results, conclusions, references, and appendices. Brevity, clarity, and proofreading are stressed.

Uploaded by

Sagar G Reddy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Technical Report Format for EECS 563

The presentation and report of any engineering or scientific work are probably as
important as the actual work. Credit for a discovery or development of new concepts
cannot be received until the work has been described in a report or paper that is readily
available for other people to read. It is often stated that engineers upon graduation will
spend their first few months of work doing about 30 percent engineering and 70 percent
writing about it. Technical writing is an important skill for engineers and computer
scientist. In numerous environments, a report is written for a specific audience. Thus, it
is important to first identify the intended audience (e.g., a supervisor as compared to a
colleague) and to recognize the type and order of information the reader is seeking. The
report format, therefore, varies. However, most reports include three essential elements:
introduction, narrative, and conclusion. Remember that brevity and clarity are
important and the report should be easy to read. All reports should be written in the third
person (e.g., use "the pressure was measured..." instead of "we measured the pressure...").
There are no excuses for misspelled words. Also, proof reading cannot be over-
emphasized. If possible, have a friend read the report for grammar, style, spelling, clarity,
and typographical errors. Also, make sure nouns and verbs agree. The report format to be
used for your simulation projects is as follows:

1. TITLE PAGE
2. ABSTRACT (See links on the web page on hints to writing an abstract)
3. TABLE OF CONTENTS
4. INTRODUCTION (See links on the web page on hints to writing an introduction)
5. BRIEF STATEMENT OF OBJECTIVE OF THE PROJECT.
6. BRIEF OVERVIEW OF SYSTEM MODEL, APPROPRIATE BLOCK DIAGRAMS
AND PARAMETERS.
7. DISCUSSION OF RESULTS (all plots and tables included in the report must be
discussed in the text).
8. CONCLUSIONS AND LESSONS LEARNED.
9. REFERENCES
10. APPENDICES (if needed)

Slighted modified from:
http://css.engineering.uiowa.edu/~expeng/labmanual/rep_format.pdf

You might also like