Show simple item record

dc.contributor.authorDavid G. Rhodes
dc.date.accessioned2017-05-08T21:20:38Z
dc.date.available2017-05-08T21:20:38Z
dc.date.copyrightJuly 2005
dc.date.issued2005
dc.identifier.other%28asce%291052-3928%282005%29131%3A3%28213%29.pdf
dc.identifier.urihttp://yetl.yabesh.ir/yetl/handle/yetl/47761
dc.description.abstractProficiency in technical writing is required of the student or professional engineer throughout his or her career. Technical writing that communicates well depends upon good organization at every level, from the details of grammar to the broad outline of structural headings and a title. Some aspects of organization in technical writing are readily prescribed by rules. Others, involving organization at a higher level, are not. This Technical Note first considers some hindrances to clearly written communication that are often overlooked in the literature. Concerned with the logical flow of ideas and with presentational form, the problems are illustrated by two examples of poor practice and suggestions for remedial action. The subject of the structural outline is then discussed and illustrated by the same examples. The emphasis of the note is that organization in technical writing is vital if the writer is to communicate his or her intended meaning and achieve the required outcome.
dc.publisherAmerican Society of Civil Engineers
dc.titleOrganization in Technical Writing
dc.typeJournal Paper
dc.journal.volume131
dc.journal.issue3
dc.journal.titleJournal of Professional Issues in Engineering Education and Practice
dc.identifier.doi10.1061/(ASCE)1052-3928(2005)131:3(213)
dc.treeJournal of Professional Issues in Engineering Education and Practice:;2005:;Volume ( 131 ):;issue: 003
dc.contenttypeFulltext


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record