How to Write About Operations Research
| dc.contributor.author | Brown, Gerald G. | |
| dc.contributor.department | Operations Research | |
| dc.date | July 19, 2004 | |
| dc.date.accessioned | 2013-11-07T20:51:09Z | |
| dc.date.available | 2013-11-07T20:51:09Z | |
| dc.date.issued | 2004-07-19 | |
| dc.description | Thesis Writing Document | en_US |
| dc.description.abstract | As an operations researcher (OR), sooner or later you will be expected to write a technical publication. The following exposes and clarifies what will be expected of you as an OR, and what you should expect from yourself. All of this applies to anything you write, from an executive summary to a full technical publication you author, or edit. Hereafter, I call this product your “publication.” You may love the mathematics, but if you cannot explain your results to a non-analyst in plain English, you have failed. As an OR, you will be expected to be better at this kind of publication than anybody else --- and, you will be. | en_US |
| dc.description.distributionstatement | Approved for public release; distribution is unlimited. | |
| dc.identifier.uri | https://hdl.handle.net/10945/37273 | |
| dc.publisher | Monterey, California. Naval Postgraduate School | en_US |
| dc.rights | This publication is a work of the U.S. Government as defined in Title 17, United States Code, Section 101. Copyright protection is not available for this work in the United States. | en_US |
| dc.title | How to Write About Operations Research | en_US |
| dc.type | Article | en_US |
| dspace.entity.type | Publication |
