
- •Elektronski fakultet
- •Written and spoken communications in english for science and technology introduction
- •Nadežda Stojković
- •Edicija: Pomoćni udžbenici
- •Elektronski fakultet
- •Nadežda Stojković
- •Isbn 86-85195-02-0
- •Table of contents
- •VI correspondence 73
- •VII spoken presentations and interviews 99
- •VIII bibliography 117
- •Foreword
- •II paragraph
- •2.1. Paragraph structure
- •2.2. Kinds of paragraphs
- •III essay
- •3.1. Parts of an essay
- •Introduction
- •3.2. Kinds of essays
- •3.3. Five paragraph model of composition
- •Introductory paragraph
- •3.4. Quotations/ references/ bibliography
- •IV formal reports and instructions
- •4.1. Formal reports format
- •4.2. Proposal (feasibility), progress and final report
- •4.2.1. Proposal (feasibility) report
- •4.2.2. Progress report
- •4.2.3. Final report
- •Introduction
- •4.3. Laboratory report
- •4.4. Design reports
- •Introduction
- •4.5. Instructions
- •4.5.1. Instructions format
- •Introduction:
- •4.6. User guides
- •Information Included in User Guides
- •4.7. Other types of technical documents/reports
- •V research papers
- •5.1. Research papers planning and writing
- •5.1.1. Note on style
- •5.1.2. General structure of a research paper
- •Introduction:
- •5.2. Journal articles
- •5.2.1. Prose and style considerations
- •5.2.2. Specific sections of an article:
- •5.3. Diploma paper
- •5.3.1. General structure of a diploma paper
- •5.3.2. Diploma paper defending
- •5.4. Master's vs PhD thesis
- •5.5. General features of a PhD thesis
- •5.5.1. Two types of PhD theses
- •5.6. PhD thesis proposal
- •5.6.1. Proposal format
- •5.7. PhD thesis format
- •Introduction
- •VI correspondence
- •6.1. Common letter components
- •Sample letter of common kind
- •6.2. Types of correspondence
- •6.2.1. Technical Cooperation
- •6.2.2. Technical Visits Abroad
- •6.2.3. Technical Visits from Abroad
- •6.2.4. Technical Training
- •6.2.5. Requesting Information
- •6.2.6. Complaint and Adjustment Letters
- •6.2.7. Application Letter
- •Sample application letter
- •6.2.8. Letter of Recommendation
- •Sample letter of recommendation
- •6.2.9. Resume/ cv
- •The common structure of a resume/cv
- •Helpful tips considering cv style
- •Sample cv
- •Your name
- •6.2.10. Cover Letters
- •Sample cover letter
- •6.2.11. Thank you Letters
- •Sample post-interview thank you letter
- •Sample post-information thank you letter
- •Sample job offer acceptance thank you letter
- •6.2.12. Memorandum
- •6.2.13. Emails
- •VII spoken presentations and interviews
- •7.1. Spoken presentations
- •7.2. Preparing and delivering formal spoken presentation
- •1) Analyse your audience
- •2) Know your task
- •3) Determine primary purpose
- •4) Shape your presentation
- •5) Select effective supporting information
- •6) Choose an appropriate pattern of organisation
- •7) Select appropriate visual aids
- •8) Prepare a suitable introduction
- •9) Prepare a closing summary
- •10) Practice
- •11) Delivery
- •12) Time and focus
- •7.3. Scientific discussion - argumentation and contra argumentation
- •6. Conclusion
- •7.3.1. Appropriate phrases for developing an argument
- •7.4. Interviews
- •7.4.1. Some interview tips
- •7.4.2. Common interview questions and answering hints
- •VIII bibliography
4.7. Other types of technical documents/reports
1. Organisational policies and procedures. These are the operating documents for organisations; they contain rules and regulations on how the organisation and its members are expected to perform. Policies and procedures are similar to instructions.
Organisations use policies and procedures documents to record their rules and regulations. These can include whatever the organisation considers important for its operations: attendance policies, substance-abuse policies, work-flow procedures, and so on. Once recorded, the policies and procedures are there for everybody in the organisation to refer to, and these documents become the means of settling most disputes within the organisation. To distinguish between these two terms, policies are general statements of how an organisation wants things to be within its walls. For example, it may have a policy that dictates eager, aggressive, do-whatever-takes customer support. But to make that policy a working reality, it will also have one or more procedures that define exactly what to do - step by step - when a customer calls with a complaint or problem.
2. Technical background reports. This type focuses on a technical topic, provides a certain background on that topic for a specific set of readers who have specific needs for it. This report does not supply instructions, nor does it supply recommendations in any systematic way, nor does it report new and original data. The technical background report does not provide step-by-step directions on how to do something the way that instructions do. It provides information on a technical topic but in such a way that is adapted for a particular audience that has specific needs for that information. Imagine the audience was a group of engineers bidding on a contract to do part of the work for a dialysis clinic. They need to know about renal disease and its therapy, but only to the extent that it has to do with their areas of expertise. Such a background report might also include some basic discussion of renal disease and its treatment, but no more than what the engineers need to do their work and to interact with representatives of the clinic.
3. Technical specifications. This type presents descriptive and operational details on a new product. Specifications are descriptions of products or product requirements. More broadly, they can provide details for the design, manufacture, testing, installation, and use of a product. You typically see specifications in the documentation that comes in the package with certain kinds of products, for example, CD players or computers. These describe the key technical characteristics of the item. But specifications are also written as a way of "specifying" the construction and operational characteristics of a thing. They are then used by people who actually construct the thing or go out and attempt to purchase it. When you write specifications, accuracy, precision of detail, and clarity are critical.