Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Typical Engineers
Day
4/24/2016
Engineering: Designing,
Designing measuring
measuring,
calculating, problem-solving
50-75%
90-95%
4/24/2016
Types of Writing
1 PERSONAL..email,
1.
PERSONAL
email letter
2. CREATIVEnovel, article
p p , thesis
3. ACADEMIC...paper,
4. TECHNICAL.manual, report
6
4/24/2016
Academic
Technical
D
Demonstrate
what
h you kknow Getting
G i something
hi d
done
about a topic
Equal to or Less than peer
reviewers
Audience:
Academia (Researchers)
Criteria for
Evaluation:
Depth,
p , logic,
g , clarity,
y, unityy
and grammar
p
Clear and simple
organization of ideas
Knowledge of
Topic:
- Michael H. Markel
Director of Technical Communication, Boise State University
4/24/2016
Encoder
(sender)
Channel
(speech,
writing,
etc.)
Message
Message
Noise possibilities
Decoder
(receiver)
N i possibilities
Noise
ibiliti
Anything that causes reader to hesitate due to
uncertainty, confusion or frustration
is noise
9
Drafting
Reviewing
Purpose
M h i
Mechanics
Readers/
Receivers
Grammar
Research
Style
Initial
Draft
Outline
Content
10
4/24/2016
Common Engineering
Documents
Wh
Whatt used
d to
t be
b done
d
b
by secretaries
t i
must now be done or managed by the
performing engineer taken from Joan Nagel
Names of common type
yp of reports
p
vary
y
considerably, but their contents combine in
different ways.
12
4/24/2016
13
Proposals
Seek a contract, approval, funding, or a bid to
get hired to do a p
g
project
j
Progress report
Summarize how your project is going
14
4/24/2016
Recommendation reports
Study a situation or problem, report on
various alternatives or options,
p
recommend
the best one
15
16
4/24/2016
17
18
4/24/2016
Background
Explain context of the report: why, who, what is the
situation time
situation,
time, date and place
Factual discussion
Combination of description and narration of facility,
what happened, where, and with whom
19
20
10
4/24/2016
21
Background
Enable readers to understand why you are doing
this work
Literature review
Discuss research literature related to your project
22
11
4/24/2016
Conclusions
Draw conclusions based on data and explain why
they are valid
23
Information sources
List information sources used
Format
Memorandum or formal report
24
12
4/24/2016
25
Specifications
Particular style, format and organization
Two columns lists or tables
Sentence style specification
Open/performance (what component do), or
closed/restrictive (what it consists of) style
Cross-reference not repeating
Use specific
p
concrete language
g g
Numerical specifications in words and symbols
26
13
4/24/2016
Specifications
Contents and organization
General description
Part by part description
General to specific (whenever applicable)
27
28
14
4/24/2016
29
Proposals
Types of proposals
Whether the recipient requested them
Solicited
Unsolicited
30
15
4/24/2016
Proposals
Contents and organization
Introduction
State the purpose and give an overview of the contents
Background
Discuss the problem or opportunity
Demonstrate your full understanding
Proposals
Contents and Organization
Method or approach
pp
Explain how to plan to go about the project
Schedule
Timeline for major milestones
Costs
Detail various expenses involved
Conclusion
Urge recipient to consider your proposal
32
16
4/24/2016
Proposals
Format
Memorandum
Short, within your company, use headings
Business-letter
Short, outside your company, use headings
Separate
p
p
proposal
p
with cover memo
Long (gt 4 pages), within your company, reviewers
34
17
4/24/2016
Progress Reports
Contents and Organization
Introduction
Purpose of topic, intended audience, overview of contents
Project description
Summarize details like purpose, scope, start and completion
dates, suppliers and clients
Progress
g
summary
y
Discuss what is completed, in progress and remaining
Three approaches: Time period, Project tasks, combined
35
Progress Reports
Contents and Organization
Problems encountered
Changes in requirements
Overall assessment of the project
Other sections
Financial data
Results of product testing
18
4/24/2016
Progress Reports
Format
Can be lengthy for large projects
Formal elements include
Title page
Table of contents
Abstract
Appendices
37
38
19
4/24/2016
Recommendation Reports
Some Distinctions
Recommendation reports
Evaluation reports
Feasibility reports
Proposals
Recommendation Reports
Contents and Organization
Description
Point-by-point comparisons
Conclusions (Summary)
Recommendations
40
20
4/24/2016
41
42
21
4/24/2016
Questions ?
43
22