White Paper Structure White papers generally have the following sections:
In general everyone writing papers is strongly encouraged to read the short and very useful The Elements of Style by Strunk and White. Here's a random list of pet peeves.
Just like a program, all "variables" terminology and notation in the paper should be defined before being used, and should be defined only once. Sometimes after a long hiatus it's useful to remind the reader of a definition.
Global definitions should be grouped into the Preliminaries section; other definitions should be given just before their first use. Do not use "etc. We shall number the phases 1, 3, 5, 7, etc. We measure performance factors such as volatility, scalability, etc.
The above rule is violated at least once in this document. Never say "for various reasons". We decided not to consider the alternative, for various reasons. Tell the reader the reasons!
Avoid nonreferential use of "this", "that", "these", "it", and so on Ullman pet peeve. Requiring explicit identification of what "this" refers to enforces clarity of writing.
Here is a typical example of nonreferential "this": Our experiments test several different environments and the algorithm does well in some but not all of them. This is important because Italics are for definitions or quotes, not for emphasis Gries pet peeve. Your writing should be constructed such that context alone provides sufficient emphasis.
People frequently use "which" versus "that" incorrectly. Examples of correct use: The algorithms that are easy to implement all run in linear time.
The algorithms, which are easy to implement, all run in linear time.White papers generally have the following sections: Title — You'll want an attention-grabbing title that clearly communicate the problem you are solving and is appropriate for your target audience.
Even for Product Knowledge white papers, it's not a good idea to include the product name in the title. Your title should be benefit, not feature, oriented.
Tips for Writing Technical Papers Jennifer Widom, The material in the abstract should not be repeated later word for word in the paper.
(Exercise: Write an abstract for the multiway sort example.) everyone writing papers is strongly encouraged to read the short and very useful The Elements of Style by Strunk and White.
Here's a random. How to write a technical white paper. Business and Commercial Moves. Don’t let your business lose any items or time during your company relocation. Our PGL Move Coordinators can pack, transport, and manage all of your belongings efficiently while keeping you in the loop.
Many papers have a submitted (and later published) conference version, along with a "full paper" technical report on the web. It's important to manage versions carefully, both in content and proliferation.
My recommendation is, whenever possible, for the full paper to consist of simply the conference version plus appendices. A white paper in the high-tech industry is a technical document that describes how a technology or product solves a particular problem.
It's a marketing document and a technical document, yet it doesn't go too far in either direction.
A good white paper is informative and is designed to show off the. While many companies think they need a white paper, few manage to write, design or use them to their full potential. This is unfortunate, because – written and applied well – white papers are one Technical stakeholders are interested in detailed feature/ Eight Rules for Creating Great White Papers.