Show simple item record

dc.contributor.authorBrown, Gerald G.
dc.dateJuly 19, 2004
dc.date.accessioned2013-11-07T20:51:09Z
dc.date.available2013-11-07T20:51:09Z
dc.date.issued2004-07-19
dc.identifier.urihttp://hdl.handle.net/10945/37273
dc.descriptionApproved for public release; distribution is unlimited.en_US
dc.descriptionThesis Writing Documenten_US
dc.description.abstractAs 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.publisherMonterey, California. Naval Postgraduate Schoolen_US
dc.rightsThis publication is a work of the U.S. Government as defined in Title 17, United States Code, Section 101. As such, it is in the public domain, and under the provisions of Title 17, United States Code, Section 105, may not be copyrighted.en_US
dc.titleHow to Write About Operations Researchen_US
dc.typeArticleen_US
dc.contributor.departmentOperations Research


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record