Students Copy Cte124 Technical Report Writing 093905
Students Copy Cte124 Technical Report Writing 093905
CTE 124
Goal: The course is design to enable students acquire basic knowledge of Technical
Report Writing.
GENERAL OBJECTIVES:
On completion of this course, the student will be able to:
1. Understand the concept of proposal writing
2. Know content of a Technical Report
3. Understand the information that is required in technical report writing
By Engr. Otobong
Onwunali
1
In order to have a good project proposal, you must put the following things into
consideration:
1. Client’s requirement: Client Requirements means the materials and/or
information which is required from the Client in order for the Company to
provide the Services, as set out in the Order Form, or as subsequently becomes
necessary from time to time in the course of providing the Services. This
requirement can vary as the project proceeds.
2. Specification: This is a general description of the system to be developed. In
the IT world there are two types of specifications namely, Software
Requirements Specification (SRS) and System Requirements Specification
(SyRS).
A Software Requirements Specification (SRS) is a document that describes what
the software will do and how it will be expected to perform. It also describes the
functionality the product needs to fulfill the needs of all stakeholders (business,
users). This involves: Define your product's purpose, Describe what you're
building, Detail the requirements. Deliver it for approval.
A system requirements specification (abbreviated as SyRS to
differentiate from SRS) presents general information on the requirements of
a system, which may include both hardware and software, based on an analysis
of business needs.
3. Proposed drawing: A schematic drawing of the system is necessary to create
a pictoral understanding of the project. The drawing may be in form of
flowcharts, entity-entity relationship diagrams, etc.
4. Cost estimates: An estimated cost of the of project materials, labour etc.
should be computed in order to determine a successful completion.
5. Execution period: A time-frame should be in implementation so as to avoid
lagging. The project should be divided into frames and a deadline should be
given to each frame to aid a successful completion of the overall project.
3
on the other hand, assist in coordination in the organization. A report traveling
between units of the same organization level (production and finance
departments) is lateral.
6. Internal or External Reports: Internal reports travel within the organization.
External reports, such as annual reports of companies, are prepared for
distribution outside the organization.
7. Periodic Reports: Periodic reports are issued on regularly scheduled dates.
They are generally upward directed and serve management control. Preprinted
forms and computer-generated data contribute to uniformity of periodic reports.
8. Functional Reports: This classification includes accounting reports, marketing
reports, financial reports, and a variety of other reports that take their designation
from the ultimate use of the report. Almost all reports could be included in most of
these categories. And a single report could be included in several classifications.
These report categories are in common use and provide a nomenclature for the
study (and use) of reports. Reports are also classified on the basis of their format.
4
executives. Conciseness is also achieved through presenting the report in brief
sections with sub-titles, rather than in one long, unbroken piece, and • avoiding
needless repetition.
6 Persuasiveness: A technical report should be very persuasive as it literally means
selling a job, but it should show no emotions of the writer.
7 Interest: The interest of the reader must be retained throughout the report without
being chatty or colloquial. This can be achieved by making it lucid.
8. Suitable Title: A suitable title has to be provided to each report according to the
nature of contents. It should also highlight upon its origin and the person for whom it
is being prepared.
9. Simplicity: The language should be as simple as possible so that the report is
easily understandable. Jargons and technical words should be avoided. Even in a
technical report there should be a restriction of use of technical terms if it has to be
presented to laymen.
10. Positivity: As far as possible, positive statements should be made instead of
negative ones. For example, it is better to say what should be done and not what
should not be done.
11. Approach: There are two types of approaches: (a) Person—When a report is
written based on personal enquiry or observations, the approach can be personal and
the sentences can be in the first person and in direct speech, (b) Impersonal—When a
report is prepared as a source of information and when it is merely factual (e.g. a
report on a meeting), the approach can be impersonal and the sentences can be in
the third person and in indirect speech.
12. Logical Sequence: The points in a report should be arranged with a logical
sequence, step by step and not in a haphazard manner. A planning is necessary
before a report is prepared.
13. Proper Form: A report must be in the proper form. Sometimes there are statutory
forms to follow.
14. Consistency: A report should be prepared for many years from the same type of
information and statistical data. If so, there is a possibility of preparing a report in
consistency. It is possible if same accounting principles and concepts are used for
collecting, classifying, tabulating and presenting the information. The usage of report
is increased through consistency.
15. Routine Details: Every report should contain the routine details like the period of
time of preparing report, the period covered in the report, date of presentation of
report, the units of information, the name of the person preparing and presenting it,
names of persons to whom it is being submitted. etc.
16. Timeliness: A report should be prepared and presented within the stipulated
time. If a report is received late, there is no meaning of preparing such report and no
use for management. If the report is presented in time, necessary actions may be
taken. Obviously financial data are more valuable when the events are fresh in the
minds of users. The element of time elapsing between the events and the report
5
determines to a large extent, the value of financial reports. Timeliness is generally
more important than a high degree of accuracy in the figures.
17. Up to Date: A report should contain latest information. Even though, excessive
information cannot be included in the report. It means that report should be kept up to
date which are necessitated by the changing conditions.
ASSIGNMENT 1
1. State two definitions of technical report
2. Differentiate between a technical report and a simple report
3. Discuss “Report is not an essay”
QUIZ 1
1. What do you understand by “a proposal”?
2. Why is a technical report a formal report?
6
Section Details
The Cover page This is the first visible page. The cover of a commissioned
technical report should be done in colour and carry the logo of
the pertinent organisation. The quality of paper varies from
glossy bond paper to treated cardboard, depending on the
funds available and the importance attached to the role of the
report in shaping the image of the organisation.
In institutions, students can design the cover page of a
technical report with “Page Borders”, name of the school, name
of the Department, the student’s registration number and
name. the title of the report, the Supervisors’ names, title of
the project and the month and the year carried out.
Title page Must include the title of the report. Reports for assessment,
where the word length has been specified, will often also
require the summary word count and the main text word count.
It should also include: name of the school, name of the
Department, the student’s registration number and name, the
title of the report, the Supervisors’ names, title of the project
and the month and the year carried out.
Acknowledgeme List of people who helped you research or prepare the report,
nts including your proof-readers.
Abstract This summarizes the contents of a report.
Summary A summary of the whole report including important features,
results and conclusions.
Contents Numbers and lists all section and subsection headings with
page number.
Introduction States the objectives of the report and comments on the way
the topic of the report is to be treated. Leads straight into the
report itself. Must not be a copy of the introduction in a lab
handout.
The sections Divided into numbered and headed sections. These sections
which make up separate the different main ideas in a logical order.
the body of the
report
Conclusions A short, logical summing up of the theme(s) developed in the
main text
References Details of published sources of material referred to or quoted in
the text (including any lecture notes and URL addresses of any
websites used.
Bibliography Other published sources of material, including websites, not
referred to in the text but useful for background or further
reading.
Appendices (if Any further material which is essential for full understanding of
appropriate) your report (e.g. large scale diagrams, computer code, raw
data, specifications) but not required by a casual reader
Presentation
For technical reports required as part of an assessment, the following presentation
guidelines are recommended:
7
Script The report must be printed single sided on white A4 paper. Hand
written or dotmatrix printed reports are not acceptable.
Margins All four margins must be at least 2.54 cm
Page Do not number the title, summary or contents pages. Number all
numbers other pages consecutively starting at 1
Binding A single staple in the top left corner or 3 staples spaced down the
left hand margin. For longer reports (e.g. year 3 project report)
binders may be used.
8
Data / Description of Data; Conclusion
Acknowledgements
References
Appendices
Provide a condensed overview of the report in the abstract. The goal of a
technical report abstract is to boil down the essentials of the report into about 300
words. You need to provide a very quick rundown of what the report covers and any
conclusions or recommendations you make in it.
Write the abstract after you have written the actual report. You want it to be a
condensed description of what you have written, not of what you intend to
write.
Check to see if there is a specific word limit for your abstract. Even if there is
not, 300 words is a good word limit to aim for.
Create an executive summary that condenses the report by about 90%.
Executive summaries get their name due to the fact that they are targeted toward
high-ranking executives who presumably would not have time to read the whole
report. The executive report should be longer and more detailed than the abstract, but
still be only about 10% of the length of the main report.
The executive summary should focus on your findings, conclusions, and/or
recommendations, and allow the report itself to present the data—although
highlights of the data should be provided.
Depending on your situation, you may need to write an abstract, an executive
summary, or both.
Draw up a table of contents, list of tables, and list of figures. The table
of contents should break down the entire report section-by-section, so readers
can quickly get a feel for the entire report and find any particular section.
Technical reports are data-driven and invariably have many tables and figures,
so provide lists of each that quickly identify them and let readers know where to
locate them.
Follow the main body of the report with an acknowledgments section.
While acknowledgements sections in books or other types of research papers
often thank friends and family, in technical reports they typically focus on
mentioning those who directly helped facilitate the creation of the report.
Use appendices to provide useful but not essential information. If, for
instance, you have a great deal of raw data that is not in itself essential to the
report, but which is enlightening nevertheless, include it in one or more
appendices. Never put anything you consider essential to the report in an
appendix—find a place for it in the main body of the work.
Use a consistent, easy-to-navigate format when creating appendices.
They are not meant to be dumping grounds for random snippets of data or
information.
Aim and Objectives: This specifies the main aim of the report, keynotes from
which conclusions can be drawn. These objectives often fall under a number of broad
groupings.
9
Scope and Limitations: You should make your scope notes clear and precise. Any
known limitations of the report should be similarly stated and hence the reservations
and precautions that have to be exercised in reading and/or using it. If such limitations
are due to specific problems encountered in the course of data collection or analysis,
you should state them explicitly.
Data Analysis: Data analysis is the method of processing and presentation of data
in a form that can be understood by the reader. This includes the use of:
(a) Graphical Method: This includes the use of graphs and charts, histogram etc.
to present data in a form that conveys information.
(b) Tabular Method: This involves the use of tables to present data in a form that
conveys information to the reader.
(c) Descriptive Method: This is the use of text to explain by describing the
information represented by the data.
Presentation of Data (Use of Appendices)
Appendices are sections at the end of academic writing with nonessential information
on the topic that still might be helpful for the reader. They typically contain charts,
graphs, maps, images, or raw statistical data.
Appendices are used to present helpful supplemental information in a way that
doesn’t distract from the flow of the main text. That’s why they typically come at the
end of a paper, set apart but still easy to find.
Appendices can include virtually any content that’s relevant to the paper’s topic
without being necessary. Usually, this consists of charts, graphs, maps, images,
videos, lists, and documentation on the research testing process (like interview
transcripts).
Each appendix should start on a separate page at the end of a paper, after the
bibliography. If you have more than one appendix in your paper, label each by letter,
as in Appendix A, Appendix B, etc. Appendices should also have a separate title that
describes their content, such as “Map of the Mongol Empire,” which is written on a
separate line.
ASSIGNMENT 2
1. Why is it necessary to follow the structure in writing a technical report
2. Differentiate between abstract and introduction
3. What do you understand by executive summary
Executive Summary
This is much more than an 'abstract' or 'summary' in a scientific paper. It is rather a
comprehensive overview of what the reader is going to find in the body of the report.
You should write it keeping in mind the busy executive who will have neither the
inclination nor the time to read the whole of your report. It is a mistake, however, to
make it so snappy that the reader is forced to refer constantly to the body of your
work in order to get the "Comprehensive overview" that you are trying to convey. It
requires considerable practice before you get the required balance right.
11
SELF-ASSESSMENT EXERCISE
Collect four scientific documents of about 50, 100, 150, and 200 pages respectively.
Beginning with the shortest document, prepare an executive summary
(comprehensive overview) of each document until you are confident of doing the
longest document with considerable ease.
Recommendations
Based on the conclusions, your recommendations are also best presented in a
numbered list and justified with the pertinent conclusions. Since this may be the only
section of your report that many important readers will have time for, you should give
12
deep thought to writing it. In particular, always remember that your recommendations
must derive scientifically from material within, not outside, the report.
End Matter
The 'end matter’ comprises material which, though important, is not essential to the
understanding or even appreciation of your report. In the interest of your self-image
as a writer, however, you should give it the same level of attention as you gave the
preliminary and main components of your report.
Appendices
This is where to place statistics, photographs, questionnaires, interview schedules,
and such other information necessary to your report but too cumbersome to include in
the main body without disturbing your trend of thought.
Acknowledgements
You should acknowledge any significant help that you received from any individual.
Specifically, you should acknowledge the source of special equipment, cultures or
other materials. Further, you should acknowledge the help of anyone who contributed
significantly to your study or to the interpretation of your data. The important element
in acknowledgements is simple courtesy.
Distribution List
Where relevant, you may include a distribution list at the end to ensure that your
report reaches all those entitled to receive it.
ASSIGNMENT
List and explain the components of a technical report.
13
Planning the report
Here is a checklist of the main stages;
Collect your information. Sources include laboratory handouts and lecture notes,
the University Library, the reference books and journals in the Department
office. Keep an accurate record of all the published references which you intend
to use in your report, by noting down the following information;
Journal article:
author(s)
title of article
name of journal (italic or underlined)
year of publication
volume number (bold)
issue number, if provided (in brackets)
page numbers
Book:
author(s)
title of book (italic or underlined)
edition, if appropriate
publisher
year of publication
Creative phase of planning. Write down topics and ideas from your researched
material in random order. Next arrange them into logical groups. Keep note of
topics that do not fit into groups in case they come in useful later. Put the
groups into a logical sequence which covers the topic of your report.
Structuring the report. Using your logical sequence of grouped ideas, write out a
rough outline of the report with headings and subheadings.
Keep them simple. Draw them specifically for the report. Put small
Diagrams diagrams after the text reference and as close as possible to it. Think
about where to place large diagrams.
Only use mathematics where it is the most efficient way to convey the
Mathematic
information. Longer mathematical arguments, if they are really
s
necessary, should go into an appendix.
15
The report layout
The appearance of a report is no less important than its content. An attractive, clearly
organised report stands a better chance of being read. Use a standard, 12pt, font,
such as Times New Roman, for the main text. Use different font sizes, bold, italic and
underline where appropriate but not to excess. Too many changes of type style can
look very fussy.
Headings
Use heading and sub-headings to break up the text and to guide the reader. They
should be based on the logical sequence which you identified at the planning stage
but with enough sub-headings to break up the material into manageable chunks. The
use of numbering and type size and style can clarify the structure as follows;
F(dB) = 10*log10(F)
……………………………………………………………………………………………… (3.6)
The Summary
The summary, with the title, should indicate the scope of the report and give the main
results and conclusions. It must be intelligible without the rest of the report. Many
people may read, and refer to, a report summary but only a few may read the full
report, as often happens in a professional organisation.
Purpose - a short version of the report and a guide to the report.
Length - short, typically not more than 100-300 words
Content - provide information, not just a description of the report.
Proofreading
This refers to the checking of every aspect of a piece of written work from the content
to the layout and is an absolutely necessary part of the writing process. You should
acquire the habit of never sending or submitting any piece of written work, from email
to course work, without at least one and preferably several processes of proofreading.
In addition, it is not possible for you, as the author of a long piece of writing, to
proofread accurately yourself; you are too familiar with what you have written and will
not spot all the mistakes.
When you have finished your report, and before you staple it, you must check it very
carefully yourself. You should then give it to someone else, e.g. one of your fellow
students, to read carefully and check for any errors in content, style, structure and
17
layout. You should record the name of this person in your acknowledgements.
18