Communication Skills 603281 Writing Skills Improving your technical

  • Slides: 49
Download presentation
Communication Skills (603281) Writing Skills Improving your technical writing Banda Ramadan-Technical writing 1

Communication Skills (603281) Writing Skills Improving your technical writing Banda Ramadan-Technical writing 1

Objective n To learn how to improve your writing skills Banda Ramadan-Technical writing 2

Objective n To learn how to improve your writing skills Banda Ramadan-Technical writing 2

Summery 1. 2. 3. 4. 5. What is technical writing Good and bad writing

Summery 1. 2. 3. 4. 5. What is technical writing Good and bad writing Characteristics of Effective Technical Writing Before you start writing Using plain English : Document style Banda Ramadan-Technical writing 3

Summery Using plain English : Document mechanics( vocabulary & spelling errors, abbreviations, and punctuation)

Summery Using plain English : Document mechanics( vocabulary & spelling errors, abbreviations, and punctuation) 7. Basic structure of a document 8. Abstracts 9. Summary and conclusion 6. Banda Ramadan-Technical writing 4

1. What is technical writing n Technical writing delivering specific information about a technical

1. What is technical writing n Technical writing delivering specific information about a technical subject to a specific audience for a specific purpose, in writing n Technical writing is meant to be practical Banda Ramadan-Technical writing 5

1. What is technical writing (cont) n Examples – – – – of technical

1. What is technical writing (cont) n Examples – – – – of technical writing: business letters Presentation materials Web applications Articles Resumes and cover letters Feasibility reports Contracts Web pages Banda Ramadan-Technical writing 6

2. Good and bad writing n Good technical writing presents useful information that is

2. Good and bad writing n Good technical writing presents useful information that is clear and easy to understand for the intended audience n Poor technical writing, on the other hand, often creates unnecessary technical jargon, and spread seeds of confusion and misunderstanding in the readers' minds. Banda Ramadan-Technical writing 7

3. Characteristics of effective technical writing n n n Clear is easily understood by

3. Characteristics of effective technical writing n n n Clear is easily understood by the intended audience without difficulties. Accurate is factual, correct, free from favors. Correct follows both grammatical and technical conventions. Comprehensive contains all necessary information. briefed is clear and complete without excess or redundant language. Accessible includes headings and subheads, indexes, Appendices, and table of contents. Banda Ramadan-Technical writing 8

4. Before you start writing n Decide what is the objective of the document.

4. Before you start writing n Decide what is the objective of the document. n Write down the objective. n Always have in mind a specific reader. n Decide what information you need to include and organize your thoughts. n Have access to a good dictionary. n Identify someone who can provide feedback. Banda Ramadan-Technical writing 9

4. 1. Decide what is the objective of the report n This is critical.

4. 1. Decide what is the objective of the report n This is critical. If you fail to do this you will produce something that is unsatisfactory n Every document should have a single clear objective n Make the objective as specific as possible Banda Ramadan-Technical writing 10

4. 2. Write down the objective Objective should be in one sentence n For

4. 2. Write down the objective Objective should be in one sentence n For example, the objective of this document is “to help students write well structured, easy-to -understand technical documents” n The objective should then be stated at the beginning of the document n If you cannot write down the objective in one sentence, then you are not yet ready to start any writing n Banda Ramadan-Technical writing 11

4. 3. Always have in mind a specific reader n You should assume that

4. 3. Always have in mind a specific reader n You should assume that the reader is intelligent but uninformed n It is useful to state up front what the reader profile is. Banda Ramadan-Technical writing 12

4. 4. Decide what information you need to include You should use the objective

4. 4. Decide what information you need to include You should use the objective as your reference and list the areas you need to cover n Once you have collected the information make a note of each main point and then sort them into logical groups n Ultimately you have to make sure that every sentence makes a contribution to the objective n If material you write does not make a contribution to the objective remove it n Banda Ramadan-Technical writing 13

4. 5. Have access to a good dictionary n Before using a word that

4. 5. Have access to a good dictionary n Before using a word that ‘sounds good’, but whose meaning you are not sure of, check it in the dictionary. n Do the same for any word you are not sure how to spell. Banda Ramadan-Technical writing 14

4. 6. Identify someone who can provide feedback Make sure you identify a friend,

4. 6. Identify someone who can provide feedback Make sure you identify a friend, relative or colleague who can read at least one draft of your document before you submit it formally n Do not worry if the person does not understand the technical area – they can at least check the structure and style and it may even force you to write in the plain English style advocated later. n Banda Ramadan-Technical writing 15

5. Using plain English: the style n 5. 1. Sentence and paragraph length n

5. Using plain English: the style n 5. 1. Sentence and paragraph length n 5. 2. Bullet points and enumerated lists n 5. 3. Using the simplest words and expressions possible n 5. 4. Avoiding unnecessary words and repetition n 5. 5. Using verbs instead of nouns Banda Ramadan-Technical writing 16

5. Using plain English: style n 5. 6. Using active rather than passive style

5. Using plain English: style n 5. 6. Using active rather than passive style n 5. 7. Using personal rather than impersonal style n 5. 8. Explain new ideas clearly n 5. 9. Use consistent naming of the same ‘things’ Banda Ramadan-Technical writing 17

5. 1. Sentence and paragraph length n n n n A sentence should be

5. 1. Sentence and paragraph length n n n n A sentence should be short A sentence should contain a single unit of information Check your sentences for faulty construction Just as it is bad to write long sentences it is also bad to write long paragraphs. You should always keep paragraphs to less than half a page. A paragraph should contain a single coherent idea If you need to write a sequence of sentences that each express a different idea then it is usually best to use bullet points or enumerated lists to do so Banda Ramadan-Technical writing 18

5. 2 Bullet points and enumerated lists n If the sentences in a paragraph

5. 2 Bullet points and enumerated lists n If the sentences in a paragraph need to be written in sequence then use a list Example: Getting to university on time for a 9. 00 am lecture involves following a number of steps. First of all you have to set your alarm – you will need to do this before you go to bed the previous night. When the alarm goes off you will need to get out of bed. You should next take a shower and then get yourself dressed. After getting dressed you should have some breakfast. After breakfast you have to walk to the train station, and then buy a ticket when you get there. Once you have your ticket you can catch the next train to Cairo. When the train arrives at Cairo you should get off and then finally walk to the University. Banda Ramadan-Technical writing 19

5. 2 Bullet points and enumerated lists n The following is much simpler and

5. 2 Bullet points and enumerated lists n The following is much simpler and clearer: To get to university on time for a 9. 00 am Lecture: 1. Set alarm before going to bed the previous night 2. Get out of bed when the alarm goes off 3. Take a shower 4. Get dressed 5. Have some breakfast 6. Walk to the tube station 7. Buy ticket 8. Catch next train to Cairo 9. Get out at Cairo 10. Walk to the University Banda Ramadan-Technical writing 20

5. 3 Using the simplest words and expressions possible Example: n Instead of saying:

5. 3 Using the simplest words and expressions possible Example: n Instead of saying: “Do not hesitate to contact us in the event that you are in need of assistance at this time”. n You should say: “Please contact us if you need help now” Banda Ramadan-Technical writing 21

5. 3 Using the simplest words and expressions possible n Words and expressions to

5. 3 Using the simplest words and expressions possible n Words and expressions to avoid are: – Replace difficult words and phrases with simpler alternatives (i. e. : utilize use) – Avoid stock and legal phrases (i. e. : At this precise moment in time Now) “The said software compiler…” “The software compiler – Avoid jargon, that is expressions like RAM, Poisson distribution, FA Cup, and distributor cap are examples of jargon. In general, jargon refers to descriptions of specific things within a specialized field. Banda Ramadan-Technical writing 22

5. 4 Avoiding unnecessary words and repetition Good Bad n n n The product

5. 4 Avoiding unnecessary words and repetition Good Bad n n n The product is not of a satisfactory nature The product is not of a satisfactory character The printer is located adjacent to the computer He wore a shirt that was blue in color Absolute nonsense n The product is unsatisfactory The printer is adjacent to the computer n He wore a shirt that was blue n Nonsense n Banda Ramadan-Technical writing 23

5. 5 Using verbs instead of nouns Bad Good He used to help in

5. 5 Using verbs instead of nouns Bad Good He used to help in the specification of new software n When you take into consideration …. n The analysis of the software was performed by Fred n Clicking the icon causes the execution of the program n He used to help specify new software n When you consider … n Fred analyzed the software n The program executes when the icon is clicked n Banda Ramadan-Technical writing 24

5. 6 Using active rather than passive style n Unless you have a very

5. 6 Using active rather than passive style n Unless you have a very good reason for the change in emphasis, you should always write in the active style n Example: – Bad: • The report was written by Ahmad, and was found to be excellent – Good: • Ahmad wrote the report, and it was excellent Banda Ramadan-Technical writing 25

5. 7 Using personal rather than impersonal style Whether to use personal or impersonal

5. 7 Using personal rather than impersonal style Whether to use personal or impersonal style is a subject that still causes fierce debate. n Some writers feel that a report is not truly scientific if it is written in the personal style. n The most important justification for using personal style is that it is more natural and results in simpler sentences. n Example: n – Impersonal: “The author’s results have shown…” – Personal: “My results have shown…” Banda Ramadan-Technical writing 26

5. 8 Explain new ideas clearly n If you are trying to introduce or

5. 8 Explain new ideas clearly n If you are trying to introduce or explain a new idea or abstract concept then there are three techniques you can use to help your readers and improve your message: – Use examples – Use analogies – Use a diagram Banda Ramadan-Technical writing 27

5. 9 Use consistent naming of the same ‘things’ n Many generations of writing

5. 9 Use consistent naming of the same ‘things’ n Many generations of writing schools have been indoctrinated with the rule: “Never use the same word twice”. n In technical and business writing exactly the opposite rule applies: You should always use the same word to refer to the same thing n Anything else causes confusion and annoyance to readers. Banda Ramadan-Technical writing 28

6. Using plain English: the mechanics n In this section we look at the

6. Using plain English: the mechanics n In this section we look at the mechanics of using plain English. We focus on: – Avoiding common vocabulary and spelling errors (Section 6. 1) – Abbreviations (Section 6. 2) – Punctuation (Section 6. 3) Banda Ramadan-Technical writing 29

6. 1. Avoiding common vocabulary and spelling errors You should always have a good

6. 1. Avoiding common vocabulary and spelling errors You should always have a good dictionary available n The following table have examples of words that are frequently misused in place of a similar sounding word with a different meaning: n affect: verb meaning to influence effect: noun meaning result or verb meaning to bring about principle: noun meaning a standard or rule of conduct principal: adjective or noun meaning most important stationery: noun meaning writing materials stationary: adjective meaning not moving ensure: verb meaning to make certain insure: verb meaning to protect against risk Banda Ramadan-Technical writing 30

6. 2 Abbreviations n The rules you should follow on abbreviations are: – Always

6. 2 Abbreviations n The rules you should follow on abbreviations are: – Always avoid abbreviating words out of laziness. For example: Never write ‘approx. ’ for ‘approximately’ – A long title, such as Tottenham Hotspur Football Club, should not be abbreviated if it is used only once in a document. However, if it is used more than once then it can be abbreviated to its initials THFC providing that the first time it is used you write the full title with the initials in brackets or vice versa – Where initials such as THFC are used as above it is useful to provide a glossary. Banda Ramadan-Technical writing 31

6. 3 Punctuation n This subsection covers the rules for using: – Capital letters

6. 3 Punctuation n This subsection covers the rules for using: – Capital letters – Apostrophes – Commas – Exclamation marks Banda Ramadan-Technical writing 32

6. 3. 1 Capital letters n The only other times you need to use

6. 3. 1 Capital letters n The only other times you need to use capitals are for: – Names ( Ahmad, Abdullah, Suha) – Organizations and places (for example, Al Isra Private University); – North, South, East and West when they form part of a country name but not otherwise (hence South Africa, but south London) – Titles when used with the name but not otherwise (hence the Duke of York, Mr. , Miss) – Certain periods of history (for example, the Iron Age) – God Banda Ramadan-Technical writing 33

6. 3. 2 Apostrophes n Apostrophes have two purposes only: 1. To show that

6. 3. 2 Apostrophes n Apostrophes have two purposes only: 1. To show that a letter has been missed out: For example, isn’t (is not), can’t (cannot), it’s (it is). 2. To show possession: For example, the snake’s eyes, the child’s shoes. Banda Ramadan-Technical writing 34

6. 3. 3 Commas If you use short sentences you will find that you

6. 3. 3 Commas If you use short sentences you will find that you need to use fewer commas. n This is a bonus, because the fewer commas you can use the better. n There are just four reasons for using a comma: n – Where you are writing a list. For example: ‘I like apples, oranges, peaches and bananas. ’ However, note that in technical reports it is usually better to use enumerated lists or bullet points. Banda Ramadan-Technical writing 35

6. 3. 3 Commas (cont) – Where you are using a qualifying word or

6. 3. 3 Commas (cont) – Where you are using a qualifying word or expression at the beginning of a sentence, such as: • However, it is best. . • For example, we can see … • Unfortunately, you should know. . – Where the sentence would be unclear without it. – To show where you have inserted a phrase. For example: “Ali, who is normally the best in the team, had a very poor match. ” Banda Ramadan-Technical writing 36

6. 3. 4 Exclamation marks There are only two reasons ever to use an

6. 3. 4 Exclamation marks There are only two reasons ever to use an exclamation mark: 1. Where there is an exclamation as in “Do it now!”, “Help!” 2. As the mathematical notation for the factorial function, as in “the number 4! Is equal to the number 24” Banda Ramadan-Technical writing 37

7. Basic structure for reports The section covers the following: n n n What

7. Basic structure for reports The section covers the following: n n n What every report should contain (Section 7. 1) General layout (Section 7. 2) Sections and section numbering (Section 7. 3) The role of introductions (Section 7. 4) Figures and tables (Section 7. 5) A checklist for when you finish writing (Section 7. 6) Banda Ramadan-Technical writing 38

7. 1. What every report should contain n Make sure every report contains the

7. 1. What every report should contain n Make sure every report contains the following basic information: – – – Title Author name(s), affiliation and contact details Date Version number Abstract (if more than 5 pages), which is essentially an executive summary – Page numbers – Table of contents (if more than 10 pages) – Conclusions (if more than 5 pages) Banda Ramadan-Technical writing 39

7. 2. General layout n One of the simplest ways to make your report

7. 2. General layout n One of the simplest ways to make your report attractive is by sticking to the following principles about fonts, spacing and margins: – Fonts: Apart from headings and caption labels, you should generally use the same font and font size throughout. – Spacing: It is good to have plenty of white space on a page. However, double-spacing throughout is too much, also you should always leave spaces between paragraphs – Margins: Leave wide margins (1. 25 in is good). For formal reports it is also best to use the ‘right justify’. Banda Ramadan-Technical writing 40

7. 3 Sections and section numbering n Any report longer than four pages should

7. 3 Sections and section numbering n Any report longer than four pages should be broken up into sections using the following principles: – Sections should be numbered – Each section should have a proper heading – Long sections should be broken up into subsections, which should be numbered – Long subsections should be broken up into subsections which should be numbered Banda Ramadan-Technical writing 41

7. 3 Sections and section numbering n Example: 1. Part One 2. Part Two

7. 3 Sections and section numbering n Example: 1. Part One 2. Part Two 2. 1 Part Two. Point. One 2. 2 Part Two. Point. Two 3. Part Three Banda Ramadan-Technical writing 42

7. 4 The crucial role of ‘introductions’ and summaries n The first section of

7. 4 The crucial role of ‘introductions’ and summaries n The first section of any report should be an introduction and overview of the entire report, and the last section should be a summary n Each section in the report also should have an introduction and a summary Banda Ramadan-Technical writing 43

7. 5 Figures and tables n It is good to include figures and tables

7. 5 Figures and tables n It is good to include figures and tables in your document because they break up the text and make it more readable. n Every figure and table in your document should be numbered and labeled Banda Ramadan-Technical writing 44

7. 6. Checklist for when you finish writing n The following checklist should be

7. 6. Checklist for when you finish writing n The following checklist should be applied before you give even an early draft of your document out for review: – Check that the structure conforms to all the rules described above – Read it through carefully, trying to put yourself in the shoes of your potential readers – Run the document through a spelling checker – Make sure you generate an up to date table of contents and references to figure and table numbers Banda Ramadan-Technical writing 45

8. Abstracts There are two types of abstracts: descriptive and informative. n A descriptive

8. Abstracts There are two types of abstracts: descriptive and informative. n A descriptive abstract says what you do in the report without providing any of the information or results n An informative abstract says what the report contains, including summarizing the main results. n An informative abstract is also called an executive summary. n Banda Ramadan-Technical writing 46

9. Summary and conclusions n No matter how poor you think your writing skills

9. Summary and conclusions n No matter how poor you think your writing skills are, you really can learn how to improve them. n Good technical writing is about using plain English. n The simpler and shorter you make things, the more likely you are to produce technical reports that get results. Banda Ramadan-Technical writing 47

9. Summary and conclusions n This Lecture has provided a number of easyto-use guidelines

9. Summary and conclusions n This Lecture has provided a number of easyto-use guidelines to help you improve your technical writing: – Have a clear objective in mind before you start writing – Keep things as simple as possible – Keep sentences and paragraphs short. – Avoid unnecessary words and repetition – Use active rather than passive style. – Use verbs instead of nouns – Use personal rather than impersonal style. Banda Ramadan-Technical writing 48

9. Summary and conclusions – Always refer to the same ‘thing’ in exactly the

9. Summary and conclusions – Always refer to the same ‘thing’ in exactly the same way – Make sure all reports conform to the basic structure described – Use examples and analogies – Use a dictionary Finally, once you have checked that your report conforms to the principles described here, have a friend whom you trust read through your report before you submit it. n Act on their recommendations, because they are likely to find the same problems that your intended audience would. n Banda Ramadan-Technical writing 49