Scribd
Upload
70 views24 pages

Techinical Report Writing: Advance English Communication Skills

This document provides guidance on technical report writing. It discusses including an introduction that states the purpose and scope. The body should provide details on the research, design, or project. Graphics and tables should be used to illustrate concepts. A conclusion section summarizes key findings. References and appendices are included to provide additional supporting information. Technical reports are an important way to document engineering projects and ensure consistent communication among team members.

Uploaded by

vinod 1990
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
70 views24 pages

Techinical Report Writing: Advance English Communication Skills

This document provides guidance on technical report writing. It discusses including an introduction that states the purpose and scope. The body should provide details on the research, design, or project. Graphics and tables should be used to illustrate concepts. A conclusion section summarizes key findings. References and appendices are included to provide additional supporting information. Technical reports are an important way to document engineering projects and ensure consistent communication among team members.

Uploaded by

vinod 1990
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 24

TECHINICAL REPORT WRITING

ADVANCE ENGLISH COMMUNICATION SKILLS


PREFACE
This project is to partial fulfillment of degree course in
ELECTRONICS AND COMMUNICATION Of ADVANCE
ENGLISH COMMUNICATION SKILLS on GROUP DISCUSSIONS
under supervision of MR.A.PARAYYA ASST.PROF(ENGLISH)
In our project we have covered all the relevant information as per
our capacity, especially on the specified domain
“TECHINICAL REPORT WRITING” .
There might be some un intentional errors and paucity in
information on the topics. I believe it may be considered as we had
to wind up our project in an acute specified time frame.
PROJECT TEAM:
6PEARLS
TEAM

A.VARUN(07811A0402),
A.ANUSHA(07811A0406),
A.B.G.SANDEEP(07811A0408),
B.R.K.SANDEEP(07811A0414),
CH.SAI KRISHNA(07811A0415),
D.VINOD KUMAR(07811A0429)
Purpose
Purpose is the reason why you are writing and if the purpose is
requirement of information related to technical concepts
it is called TECHNICAL REPORT WRITING.

•Most of scientific and technical writing are either


informational or instructional
Example:
In purpose If your report's purpose is to create an artefact, then
you have to present all the technical aspects of the design. This
way, someone can read the report and build your artefact. You
have to be aware of very fine details whenever you write a report.
Technical Report
Includes
•Presentation of facts and conclusions about your designs and
other projects
•Information about research which is related to technical
concepts, graphical depictions of designs and data
•Following of a strict organization
•Quick location of the information that interests
reader the most
Report Content
Many designs begin with identifying the problem,
determining the goals, and creating a list of
alternatives. The next part is the evaluation. This
includes the technical, legal, economic, financial,
environmental, and social evaluations. Then you
make recommendations based on these evaluations.
Most reports, especially design reports include this
information.
Purposes and Strategies
A purpose is the aim or goal of the writer or the written
product; a strategy is a means of achieving that
purpose.
For example, our purpose may be to explain something,
but we may use definitions, examples, descriptions, and
analysis in order to make our explanation clearer. A
variety of strategies are available for writers to help
them find ways to achieve their purpose(s).
Laws for a Technical Report
1. The reader is the most important person.
2. Keep the report as short as possible.
3. Organize for the convenience of the report user.
4. All references should be correct in all details.
5. The writing should be accurate, concise and unobtrusive.
6. The right diagram with the right labels should be in the right place for
the reader.
7. Summaries give the whole picture, in miniature.
8. Reports should be checked for technical errors, typing errors and
inconsistency.
9. The report should look as good as it is.

All above laws can be broken in


…tradeoff with the FIRST law
Graphics

•Graphics provide illustrated information to readers.


•In general, graphics are designed to make it easier for
readers to understand your report
•Fitting your description within a few paragraphs is
impossible, so you decide to create a graphic
Audience:
You shouldn't always assume that your audience
has a strong engineering background or is familiar
with the engineering terminology you use.
Always check with your instructor to know who
your audience is.

Engineers with a background similar to yours is


more likely to understand the terminology you
use. However, you should always evaluate who
your readers will be in advance.
In communication they usually
define audience as:

•Technical audience
• Semi-technical audience
•Nontechnical audience
General Format
Technical Reports have an organized
format because a majority of your
audience may not read the entire report
in one reading. This specific format
allows readers to quickly locate the
information they need.
Transmittal Letter
Transmittal letters often accompany reports and
inform readers of a report's context.
Typically, the letter includes information not found
in the report
Example:
recipient's address, your address, a salutation and
closing, contact information
Title Page
A technical report should always include a title clearly
identifying the report.
A title should be descriptive and accurate, but not wordy,
verbose or too terse.

Example:
• CSU Performing Arts Center
• MASK Engineering
• Fort Collins, Colorado
Abstract:
The Abstract is extremely important because it helps
readers decide what to read and what to pass over.
The most important purpose of the Abstract is to allow
somebody to get a quick picture of the report's content and
make a judgment.
For example, if your report is 8 pages long,
you shouldn't use more than 150 words in the Abstract.
Generally, Abstracts define the report's purpose and content.
Executive Summary:
•Typically, Executive Summaries are written for readers
who do not have time to read the entire technical report.
•An executive summary is usually no longer than 10% of
the report.
•In the executive summary, you should summarize the
key points and conclusions from your report.
List of Figures and List of Tables
These two separate lists assist readers in locating
your photos, drawings, tables, graphs and charts.

Like the Table of Contents, you need to present both


of these in an organized, appealing format.
Report Body
In a technical report, the body typically presents an
Introduction, various other sections, depending on your
topic, and a Conclusion.
Throughout the body, you should include text, graphics,
and lists.
Whenever you cite information or use graphics from
another source, you must credit these sources within
your text.
Check with your instructor to know which reference
style to use.
Writing Technical Design Reports as a Group

Often, technical design reports require that multiple


experts help write them. This is called "concurrent
engineering.“
This way, everyone involved with a project contributes.
More ground gets covered this way.
The report is also a good way to document a design.
Then, if problems arise later, everyone can refer to the
document.
This helps determine where changes were made, etc.
Multiple Reports for a Project
Suppose your engineering task is to build a retaining wall.
As the main engineer, You'll write a report where you
state the goals and how they will be accomplished.
Next, soil engineers may actually test the soils at the
location.
They would then produce a report about what they found.
Every project generates multiple reports.
Appendices
•Appendices include information that is too large
to fit within your report, yet information necessary
to your report.
•For instance, six pages of calculations would
obviously cause readers to loose their train of
thought.
• Appendices always appear at the end of a report.
References
Whenever you cite information (this includes graphics)
from another source, you must credit the source in your
References.

Example:
• References
• The Book Division, National Geographic Society, 1992, 50,
74-5.
•
• Newhouse, Elizabeth L., ed. The Builders: Marvels of
Engineering.
Any QUEIRIES

???
Than k U !

You might also like