that contains: • A methodology to explain what

The intent of the assessment is for you to demonstrate that you can produce a high-quality document that accurately and succinctly details ALL the important aspects of your work. Thus the thesis is a comprehensive technical document that contains: • A methodology to explain what you have done and how you have done it • The results and outcomes from the project explained and presented using appropriate figures. • A critical discussion of the relevance and implications of the results and outcomes • Conclusions and recommendations for future work. Conclusions A review of major findings and results of the work are given here. Recommendations This indicates further development and work. References Please include all material that is referred to in your main text. Bibliography This is a list of articles or books for further reading on the subject of the report to which no reference has been made in the text. When listing these works the same format should be adopted as for references. Writing Style The underlying principle which should govern your writing style is that of persuasive communication. You should be simple, clear and unambiguous; long winded sentences should be avoided (i.e. less than three lines on a page). Avoid padding the text with unnecessary adjectives and phrases. Jargon and acronyms should be explained where they first occur. If necessary a glossary of special terms can be provided as an Appendix. It is presumed you will use a word processor to produce your report so remember to use the spell-checking and grammar facilities. A report with spelling errors leaves a bad impression and can lose marks. A good thesaurus can help you find alternatives to either simplify a sentence or to avoid the overuse of a particular word. No matter how careful you are, proof reading is still essential to catch errors such as ‘their’ for ‘there’ and ‘it’s’ for ‘its’. You should avoid referring to yourself; ideally you should depersonalise the report completely. This can read quite naturally when properly handled, e.g., ‘A program was developed…’ rather than ‘I developed a program…’. This approach can also help reduce the word count. In her book “Bugs in Writing”, Lyn Dupré (1998) lists 150 principles to writing good technical documents.

Leave a Reply

Your email address will not be published. Required fields are marked *