Technical Writing

WikiAnswers contributors share their take:

• Technical writing is a matter of writing documents that explain or accompany products. It's flexible work, but often considered very monotonous and boring.
• Not every writer can be a technical writer, just as not every writer can be a novelist. The goal of technical writing is always clarity. Technical writers want to write so there is the least possible chance of misunderstanding. Technical writers may also be responsible for designing graphic aids (diagrams, illustrations, charts, graphs and the like) to help explain things.

  Technical writing rarely has a "style" - or rather, the style is so transparent that readers aren't really aware that the text was "written". Larger companies that produce a number of products (Microsoft, for example) have in-house technical writing teams and style guides. Smaller companies may hire out technical writing to independent contractors.

• Technical writing is the art of being able to explain/describe complex ideas to both technical and nontechnical audiences usually in the form of a Manual. This could range from describing a complex procedure to maintain a specific type of military apparatus to explaining how to assemble a baby's playpen to a consumer. In all cases, technical writing must be succinct, accurate, comprehensive and easy to understand and follow. Personalization such as humor should not be included in technical writing.

What does the future hold for us? Well, change and competition are constants, so clearly we will have to adapt to ever-more sophisticated tools and media. Where today we have to concern ourselves with certain nuts and bolts, soon we won't in the way that hardware engineers no longer handle soldering irons or individual components. Today touch screens and mobile-device interfaces are new, but they will become passé soon enough. Also, we will have to adapt to understanding new subject areas. (Don't ask me what they'll be. As my stock portfolio demonstrates, I have no idea.)

Information is a strategic asset and potential competitive advantage.

Today few companies realize it, but Information is a strategic asset and potential competitive advantage. In the near future many more companies will realize it, and I think it will cause them to hold these assets more closely and not outsource their development. Also, this will open the way for technical communicators to be information managers.

Increasingly, I think our role will be subsumed into the general work of product development. The more information is seen as a component of the product, the more we will be seen as part of the development team. I think that will be a positive development.

Today there are European Union (EU) regulations concerning the presence and structure of information for consumer products; the FDA has strict requirements for the documentation of medical products. Few writers know that there are International Organization for Standardization (ISO) standards for software documentation and the process of creating it. These regulatory and standardization pressures will only increase. In the future, we will likely be required to know and implement them in our work.

Finally, just as there are increasing pressures on companies to demonstrate their conformance to standards, we will increasingly need to provide assurances before we're hired that we are competent. We can meet this challenge through specific education or, in my opinion, some form of certification.

To continue serving its members, STC will need to lead the way in publicizing the strategic value of information and how we can maximize it; provide education and training on new regulations and standards (and help shape them!); and determine how best to assess practitioners.

You just write down the name of the person or organization and what they did to help, such as "I would like to thank Mr Tyler, Mrs. Jane, and Mrs. Price for guiding my experiment. I would like to thank Dr Fisher for helping analyze data. lastly I would like to thank Mrs Glass keeping the library open past hours to help find the books i needed....

If it is more formal, such as a scientific paper, you list the names, resources and contributions, like a 'works cited' sheet for people.

Also, remember to thank any organization or individual that provided money or technical assistance for the research. Some organizations providing research funds require you to give the reference number of any grant. In such cases you will presumably have been informed.
I am very thankful to everyone who all supported me,for i have completed my http://wiki.answers.com/q4163395.htmleffectively and moreover on time.

I am equally grateful to my teacher[name].she gave me moral support and guided me in different matters regarding the topic.she had been very kind and patient while suggesting me the outlines of this project and correcting my doubts.I thank her for her overall supports.

Last but not the least, I would like to thank my parents who helped me a lot in gathering different information, http://wiki.answers.com/Sports_Leisure/Hobbies/Collecting/data and guiding me from time to time in making this project .despite of their busy schedules ,they gave me different ideas in making this Answers.comunique.

Thanking you

name

class-sec

this is how i wrote my project acknowledgement.

1. Clarity. To make your documents clear: * Provide specific detail * Answer the reporter's questions * Use easily understandable words * Use verbs in the active voice 2. Conciseness. To save your writer's time: * Limit paragraph length * Limit word and sentence length * ** Avoid a high fog index ** Use meat cleaver method of revision ** Avoid shun words ** Avoid camouflaged words ** Avoid the expletive pattern ** Omit redundancies ** Avoid wordy phrases 3. Accuracy. To avoid grammatical errors follow proofreading tips: * Let someone else read it * Let the document sit before proofreading * Read backwards * Read one line at a time * Read long words syllable by syllable * Use computer spell checks * Check figures, scientific and technical equations, and abbreviations * Read it aloud * Try scattershot proofing * Use a dictionary 4. Organization. To guide your reader, use organizational strategies:

* Spatial * Chronological * Importance * Comparison/Contrast * Problem/Solution 5. Ethics. To be a responsible technical writer: * Check your actions against legal, practical, and ethical concerns * Follow strategies for making ethical decisions: define the problem, determine your audience, maximize values and minimize problems, consider the big picture, and write your text

1. Always have in mind a specific reader, real or imaginary, when writing a report; and always

assume that this reader is intelligent, but uninformed.

2. Before you start to write, always decide what the exact purpose of your report is, and make sure that every paragraph, every sentence, every word, makes a clear contribution to that purpose, and makes it at the right time.

3. Use language that is simple, concrete, and familiar.

4. At the beginning and end of every section of your report check your writing according to this principles: "First you tell your readers what you are going to tell them, and then you tell them what have told them."

5. Make your report attractive to look at.

Here are additional 5 Tips on how to write a good capstone paper, since final exams are approaching and it will be about time for submission.