dc.contributor.author | Detwiler, Rachel J. | |
dc.contributor.author | Darwin, David | |
dc.date.accessioned | 2017-03-09T19:18:31Z | |
dc.date.available | 2017-03-09T19:18:31Z | |
dc.date.issued | 2001 | |
dc.identifier.citation | Detwiler, R. and Darwin, D. “How to Write a Good Technical Paper,” Concrete Interational, Vol. 23, No. 9, Sep. 2001, pp. 52-55. | en_US |
dc.identifier.uri | http://hdl.handle.net/1808/23381 | |
dc.description.abstract | The ability to communicate is a critical skill that not only affects our success as professionals, but also determines how
effectively lessons from the laboratory and field are transferred into general practice. As members of ACI's Publications Committee, and as authors ourselves, we offer some guidelines on one form of communication: writing technical papers.
You can apply the principles we discuss to formal technical reports, reports to clients, conference papers, and journal articles. Publishing organizations prescribe the exact details of form and format. Because a technical paper should reconstruct the process of the investigation, the generic outline of a paper closely resembles the steps of the scientific method:
1. Identification of the problem or question to be investigated; 2. Evaluation of previous work in the field; 3. Formulation of the hypothesis or definition of the key aspects of the investigation; 4. Design of experiments, observations, or both; 5. Gathering of data; 6. Evaluation of data; and 7. Presentation of conclusions. | en_US |
dc.publisher | American Concrete Institute | en_US |
dc.relation.isversionof | https://iri.ku.edu/reports | en_US |
dc.title | How to Write a Good Technical Paper | en_US |
dc.type | Article | en_US |
kusw.kuauthor | Darwin, David | |
kusw.kudepartment | Infrastructure Research Institute | en_US |
kusw.oastatus | na | |
dc.identifier.orcid | https://orcid.org/0000-0001-5039-3525 | |
kusw.oaversion | Scholarly/refereed, publisher version | en_US |
kusw.oapolicy | This item does not meet KU Open Access policy criteria. | en_US |
dc.rights.accessrights | openAccess | |