Thanks to visit codestin.com
Credit goes to www.scribd.com

100% found this document useful (1 vote)
850 views15 pages

Technical Report Structure Guide

The document outlines the typical structure of a technical report, including sections for objectives, experiments, infrastructure, measurements, and prototypes. It describes the common elements found in each section, such as the purpose of an introduction, content in the body, conclusions drawn, and recommendations provided. The technical report structure is meant to clearly convey technical information and results from a research project in an accessible format.

Uploaded by

Angel Dianne
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
100% found this document useful (1 vote)
850 views15 pages

Technical Report Structure Guide

The document outlines the typical structure of a technical report, including sections for objectives, experiments, infrastructure, measurements, and prototypes. It describes the common elements found in each section, such as the purpose of an introduction, content in the body, conclusions drawn, and recommendations provided. The technical report structure is meant to clearly convey technical information and results from a research project in an accessible format.

Uploaded by

Angel Dianne
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/ 15

EAPP- Year 11 HUMSS

Technical
Report
Various Kinds of Reports
Technical Report
is a document written by a researcher detailing the results of project that
needs different approaches of data collection and treatment to convey
technical information in a clear and easily accessible format. Technical
report is not peer-reviewed unless they are subsequently published in a
peer-review journal.
Objectives
2 4
1 3 5
Information- Experiments- Infrastructure- Measurement and
Prototypes-
Research or conducting of Tools that can calculation-
Building out
the acquiring experiments be used by the Developing
elements of a
of data. of test people to measurements,
solution to gather
achieve goals. calculations, metrics,
information such as
reports and
user feedback or to
benchmarks.
confirm feasibility
Structure
LETTER OF TRANSMITTAL
The components of a report are not written in the same order in which the last to be
created. It introduces the purpose and content of the report to the principle reader. It
gives you an opportunity to emphasize whatever you think: your reader will find
particularly in theattached material. It enables you to point out any errors or
omission in the material. Transmittal letter contains the following element.
•A statement of title and purpose of report.
•A statement of who authorized the project and when
•A statement of method used in the project or of the principal recommendations
•An acknowledgement of any assistance you received in preparing the material.
Structure
TITLE PAGE
Usual elements of title page in a technical report are:
•Title
•Name and position of writer
•Date of submission
✓ A good title must be informative. It answers two basic questions:
1. What is the subject of the report?
2. What type of report is it? Eg. sea pollution-control devices
Define the type of report by using a generic term such as analysis, recommendations e.g
summary, review etc. For a simple title page, center the title (typed in full capital letter)
about a third of the way down the page, then add the readers and writer's position, the
organization's name and date.
Structure
ABSTRACT

is like a brief technical summary, usually not more than 200 words of the report. Its
directed to readers who are familiar with the technical subject and need to know
whether to read the full report or not. This can use technical terminology and refer
to advanced concepts. Basic types of abstract are descriptive and informative
abstracts. The descriptive abstract sometime called topical or table of contents
abstract. It does not provide the import results, conclusion or recommendations. It
lists the topic covered giving equal coverage to each. The informative abstract states
the problems the scope and methods, and the major results, conclusion or
recommendations.
Structure
TABLE OF CONTENTS

The table of contents in the technical report structure enables different readers to
turn to specific pages to find the information they want. Well organized report
becomes ineffective if table of contents, is not clear. T.O.C provide only guide to
report's structure, coverage and pagination. The headings that appear in the report
are listed in T.O.C. For effective T.O.C make sure the report has effective headings
Structure
EXECUTIVE SUMMARY

Sometimes called executive overview or the management summary in the technical


report structure. It is a one-page condensation of a report. Managers don't need a
detailed and deep understanding of various projects undertaken in their
organization because of limitations in time and specialization. The background of the
project is also discussed clearly herein. The specific problem that is to be solved
through the project is clearly discussed; also the conclusion and recommendations
are discussed in a full separate paragraph.
Structure
GLOSSARY AND LIST OF SYMBOLS

A glossary is an alphabetic list of definitions. It is useful if you are addressing a


multiple audience that includes readers who will not be familiar with the technical
vocabulary used in the report. An asterisk or any other notation can be used along
the word to tell the audience that the word is defined in glossary. It is generally
placed at the end of the report just before the appendix. Though if the glossary is a
brief one, so can be placed right after the table of contents. A list of symbols is
structured like glossary, but rather than defining words and phrases, it defines the
symbols and abbreviations used in the report. Like glossary, the list of symbols may
be placed before the appendices or after the table of content.
Introduction
This section gives the reader the necessary background information and
leads straight into the report itself. A typical introduction can include the
following content:

•Main aim/s, objective/s and scope (the parameters) of the report


•Identify the importance of the current project for scientific knowledge or
commercial operations
•An overview of the report's sections
•Method(s) of approach
•Indications of scope and limitations of the study
•Outline of material presented in rest of report.
Body
This will include all the main content of the report like what task was
at hand, what were the findings, what methodology was used to find
the findings, comparison and discussion of the results. This is usually
the longest and most important part in the structure of the report so
the material must be presented logically to make it is easy to read. It is
divided into numbered and headed sections. These sections separate
the different main ideas in a logical order.
Conclusion
It answers the questions raised by the original research
problem or objectives of the study. The conclusions should be a
condensed version of the intervening sections giving the key
findings of the work. No new scientific argument should be
presented here everything should have already been discussed
in the "Discussion".

•Reference to original aim(s) and objective(s) of report,


•Limitations and advantages of the findings,
•Objective opinion, evaluation or judgement of the evidence

The conclusion must arise from the evidence discussed in the


body of the report. It should not, therefore, subjectively tell the
reader what to do, this job is performed by the
recommendations section.
Structure
RECOMMENDATIONS

Recommendations tell the reader what to do: what decision to make, what course of
action to take, what solution is superior or what further work needs to be
undertaken.The recommendations section should never contain any new evidence
and should arise from the information presented in the body and conclusion
sections.Recommendations in the technical report structure should be feasible and
appropriate to the problem; for example, their cost should be realistic to the budget
and they should be ethical. They should be as concrete and specific as possible; they
should read as a list of things the client should do. They can be written in descriptive
as well as bullets form, whatever is desired. Let your reader know why you are
recommending an action by supplying the reasons for your decision drawn from the
conclusions of the report.
Structure
APPENDIX

In the technical report structure, an appendix is any section that follows the body of
the Appendix report (and the list of references or bibliography, glossary or list of
symbols).Appendices provide information that is too bulky to be presented in the
body or that will interest only a small number of readers. For conciseness in the
report, this information is separated from the body. Examples of the kind of material
that are usually found in the appendix include maps, large technical diagrams or
charts,computations, test data and texts of supporting documents. Appendices are
usually lettered, rather than numbered and are listed in the table of contents.
Group 2 : Fieror,Latupan,Laguinday,Gundan,Gammad,Callueng,Favor,Taguba,Ramos
Klien Johnmark Aron Denver

Myra
Cristina Felisa Angel
Shyrine

You might also like