Professional Documents
Culture Documents
Lecture Overview
z z z z
Purpose of Technical Writing Proposal Characteristics General Tips on Default Style Tips on Prose Style
CSC633
4/18/2007
to an audience that can make use of it in a level of detail appropriate for that audience Algorithm System component (hardware, software, protocol) Performance eval. (analytical, simulated, measured) Theoretical framework (theorems, lemmas, etc) System model (way of looking at an object)
CSC633 3
Types of results
z z z
z z
Tends to be very formal and precise style (3rd person) Novelty of results is of interest to a large audience Like above Synthesize existing results for researchers or students Often precedes formal publication; also formal and precise Results may be of interest only in-house More proactive, positive style (1st person) Must sell the idea on its technical merits
Review Papers/Tutorials
z z
Technical Report
z z
Grant Proposal
z z
CSC633
4/18/2007
Proposal Characteristics
z
Straightforward document
z
The first words you write are the most important ones Clear, sharp and precise economy of words; no rambling sentences Outlined with proper use of headings and subheadings
Clearly organized
z
CSC633
Background information; problem description in context Hypotheses or objectives Assumptions and limitations Significance or Importance and benefits
z z z z z z
Related Work/Literature Review Research Methodology Plan of Work and Outcomes (deliverables, schedule) Conclusions and Future Work References Budget (appendix)
6
CSC633
4/18/2007
Abstract
z
Reader must be able to quickly identify content Helps reader decide whether to read the paper problem significance approach results
Briefly summarize
z z z z
CSC633
Problem Statement
z Convince
z
CSC633
4/18/2007
Research Objectives
z Flows
z
z Verify
z
checking to see that each objective is discussed in the research design, data analysis and results sections
9
CSC633
Literature Review
z Recent
studies z Always refer to the original source z Discuss how the literature applies, show the weaknesses in the design, discuss how you would avoid similar problems z How is your idea different/better?
CSC633
10
4/18/2007
of the doing the study now z What are the potential impact on
Research in the area z Applications z Larger community
z If
you find this difficult to write, then most likely you have not understood the problem
CSC633 11
May contain many subsections Be specific about what research methodology you will use and why Provide details of your proposed solutions to the problem and sub-problems Provide information for tasks such as sample selection, data collection, instrumentation, validation, procedures, ethical requirements
CSC633
12
4/18/2007
Schedule or Planning
z Include
the major phases of the project z exploratory studies, data analysis, report generation z Critical Path Method (CPM) of scheduling or Gantt chart may help
CSC633
13
Deliverables
z Measurement
CSC633
14
4/18/2007
a reviewer or reader may start by reading the Introduction and Conclusions first Clearly state where we can go from here
z z
shows the work has a future invites participation from the readers
CSC633
15
to special systems or computers z specialized computer algorithms z Itemized Budget z Budget Narrative
z This
CSC633
16
4/18/2007
if a figure is too big, break it into smaller figures add a figure to hierarchically decompose it walk the reader through the figure or table clearly state the results you want the reader to see clearly state the relationships between related figures one good figure really is worth a thousand words a thousand bad figures are worth nothing
CSC633
17
if necessary, insert special section after References use hand-drawn figures only as a last resort Locate figure after paragraph containing 1st reference Do not refer to the following figure (they may move) e.g., Figure 1: 1998 Gnu-to-Gnat Population Ratios Generally located under a figure but above a table
CSC633
18
4/18/2007
Appendices
z
Data that would disrupt the flow of the main text, Data the casual reader does not need, e.g.
z z z
Huge figures Large tables of raw data Complete source code listings
z z z
Limit each appendix to 1 major topic Each must be lettered, and cited in the text by letter Remember, page numbers must be globally unique
CSC633
19
Do not use footnotes for references Footnotes are used for parenthetical comments Alphabetical by last name of first author In order of citation in the paper All references in the list must be cited in the text All references cited in the text must be listed
CSC633 20
10
4/18/2007
Plagiarism
z z
The use of someone elses intellectual property without proper citation of the source. Includes:
z z
Text: direct quotes or very close paraphrasing Ideas: concepts, definitions, observations, results, data, facts, claims, recommendations, etc. Figures or Tables: even if you redraw them
CSC633
21
Also, look at recent issues of the target publisher or other sample proposals. incorrect style may it is rejected without being read
z z
especially true for grants & more competitive pubs no reviewer wants to read single-spaced 10-pt. font
Visual Presentation
z z
should be clear, clean, professional avoid cutsy, artsy, or overly distracting cosmetics
CSC633 22
11
4/18/2007
z z z
One inch margins all around Single-column format Professional looking font
z z z
e.g. Times New Roman or LaTeX \rm font 12-point for normal text Dark, black, letter quality print (no dot matrix)
CSC633 23
Double-space or 1.5-space
z z
much easier to read allows room for reviewers comments Use some! Leave a blank line between paragraphs Indenting the 1st line is optional On-line submission even better
24
Paragraphs
z z z
CSC633
12
4/18/2007
all numbers must be globally unique all must be in lexicographically increasing order, e.g.
z z
1, 2, 3, 4 I-1, I-2, I-3, II-1, II-2, II-3 (for very long reports)
must be globally unique and hierarchical, e.g. 1.3 Gnus and Gnats 1.3.1 Gnus 1.3.2 Gnats I.C Gnus and Gnats I.C.a Gnus I.C.b Gnats
CSC633
25
Prose Style
z Generally
z
Draws attention to the topic, not the author z Passive voice is quite common,
e.g. the intermediate results are then passed from the ALU to the register bank z heavy use of forms of to be flags passive voice
z
13
4/18/2007
Prose Style
z Use
z Generally
z
Prose Style
z Use
z
Future tense:
z
z Do
14
4/18/2007
Prose Style
z z z z
When used in-line, numbers 10 are spelled out Avoid excessive mathematics in-line Equations need some explanatory text Always define an abbreviation at its first use
z z
e.g. the Command and Control Bus (CCB) exceptions: universal terms (RAM, ROM, CPU)
z
If you have not used a term for several pages, then redefine it when it is reintroduced.
CSC633 29
Prose Style
z z z z
Be absolutely consistent with important terms Use variation in the little grammatical stuff, e.g.
z
e.g., = for example = such as their meaning can get lost easily Short clear sentences = good, Long convoluted sentences = bad, Incomplete sentences = worse.
CSC633 30
15
4/18/2007
Prose Style
z
Use parenthetical remarks sparingly (as they tend to interrupt the flow of the sentence)
z z
keep them short, find the least disruptive place to put them in the sentence,
no more than 1 or 2 on a given page no more than a handful in the whole paper
CSC633 31
Closing Comments
z z z z
When in doubt, follow publishers instructions When in doubt, cite the source Spelling and Grammar checkers:
z
Use them, but dont trust them implicitly use one pick one whose English is better than yours
Outside proofreaders:
z z
Remember, the reviewer doesnt really want to read this paper. Dont give him/her an excuse to quit.
CSC633
32
16