Acrobat PDF

Guidelines for the preparation of project reports

You must be logged in to download this document
Reviews
Shared by: hongkonguniv
Stats
views:
19
downloads:
0
rating:
not rated
reviews:
0
posted:
8/4/2008
language:
English
pages:
0
Submissions and Preparation of Projects Reports The University regulations require : "Each copy of a dissertation shall be type-written or printed on one side only of International size A4 paper (except for drawings, maps, or tables on which no restriction is placed), with a margin of not less than 38mm on the left-hand edge of each page. While the quality of a project does not necessarily depend on its size, it is desirable that the report itself should appear to be substantial. I would expect a minimum of 100 pages (including all appendices) of normal double spaced typing. You should remember that the report is for an academic degree. It is thus essential that it should include a good list of references, and that the references be discussed and evaluated in the report. To help the examiners with the task of grading your report, you should clearly state the aims and objectives in the early part of the introduction. A draft copy should be submitted to your supervisor for final discussion and amendments. As it takes time to read these reports, you should submit the draft to your supervisor at least 1 month before the final date. The contents of the first few pages should be as shown on the attached example. Your project title will have to be approved by the Engineering Faculty Board, and you will receive a letter from the Faculty Secretary once the title is approved. Also remember that most authors find it difficult to proof read their own work. It is always a good idea to get a professional to proof read the report and to correct general grammatical/typographical errors. I have attached the address of one such person that does this type of work, but, of course, there are many others. Students are required to have 3 hard copies of their report signed by their supervisors on or before the final date. The signed copies must then be taken to the Library for binding. The Library will inform you when the binding is finished, some 7 to 14 days later. You should then collect the bound copies from the Library and bring them to your supervisor. D. Sculli September, 2002 Automation at Final Assembly of Portable Radios A Feasibility Study by LEUNG Wai Ming (University Number: 1988242529) This report is submitted in part requirement for the Degree of Master of Science (Eng.) in Industrial Engineering and Industrial Management. University of Hong Kong 1983 - i - This report has been approved for binding and submission to the examiners. Signed: (Mr. D. Sculli) Date: Supervisor This report is an examination script and must not be reproduced in whole or in part without the written permission of the Head of Department of Industrial and Manufacturing Systems Engineering, The University of Hong Kong. - ii - I, Leung Waiming, hereby declare that the M.Sc. project report, entitled "Automation at Final Assembly of Portable Radios - A Feasibility Study", which I am submitting, represents my own work and has not been previously submitted to this or any other institutions in the application for admission to a degree, a diploma or any other qualifications. Signed: Leung Wai Ming Date: - iii - ACKNOWLEDGEMENTS Acknowledgements are optional and if you don't need to make any, you should remove this page and renumber subsequent pages. Should your report contain data from your company or organization, you can acknowledge this with a short statement like: I would like to thank Company XXX for allowing me to use their data in this report. - iv - ABSTRACT This abstract should be about 200 to 400 words long. It should be an abbreviated, accurate representation of the contents of the report. Major results, conclusions and/or recommendations should be given, followed by supporting details of method, scope or purpose, as necessary. - v - INDEX Contents Declaration Acknowledgement Abstract Chapter 1 1.1 1.2 1.3 1.4 Chapter 2 2.1 2.2 2.3 2.4 " " References Appendix 1 Program listing of C2.PAS Appendix 2 Sample output listing Appendix 3 Diagrams for experimental networks Appendix 4 Data for experimental networks Problem overview Introduction Aims and objectives Historical background Fundamentals and issues Methodology and solutions Exact solutions Approximating techniques Bounding techniques Simulation techniques " " Page ii iv v 1 8 14 20 26 38 49 59 " " 240 243 252 254 264 - vi - Guidelines for the Preparation of Project Reports 1. INTRODUCTION A good report should be readable, interesting and well presented. Naturally the treatment will vary greatly according to the nature of the work done; nevertheless certain standards are generally applicable. 2. FORMAT The report should be type-written or printed on one side only of A4 size paper (except for drawings, maps or tables on which there are no restrictions) with a margin of at least 38 mm on the left hand side of each page. 2.1 Abstract (or summary) of the report should, in one page, include: the purpose of the study; the methodology used; and a summary of the major findings, conclusions and recommendations. 2.2 Contents page giving a list of all sections of the report, with major and minor headings and the number of the page on which each section begins. If your report contains a lot of tables, graphs or figures, list them on the contents page so the reader can locate them easily. 2.3 The main body of the report should be organized into logical parts or sections that follow along in an orderly manner. 2.4 Headings. Main heading should be in capitals and numbered. Second-order headings should be flush with the margin and underlined with only the initial letter capitalized. If third and higher order headings are used they should be underlined and indented to begin the paragraph (as in 2.4.1 above). Avoid excessive use of minor headings. 2.5 Reference citations in the text should be in brackets giving the author(s) surname(s) and year of publication. If the name of the author occurs in the text, the year should be in brackets. References are not cited just for the sake of creating a reference list. The quality of a project will, to a large extent, depend upon the ability of the student to relate his work to the relevant literature and to make a critical examination of that literature e.g. A recent study (Chi and Drury, 1988) made assumptions which may apply here but ..... Turner et al (1988) use a method which is not suitable here because ..... Your REFERENCE list at the end of the report should be accurate. Make sure there is enough information for the reader to find the exact piece of writing referred to. Give the references in alphabetical order, showing author(s), year, title, source and (usually) page numbers e.g. Turner, W.C., Mize, J.H. and Case, K.E. (1987). Introduction to Industrial and Systems Engineering (2nd. ed.). New Jersey: Prentice Hall. pgs. 412-416. Chi, C.F. and Drury C.G. (1988). A Further Note on Psychophysical Testing of Handles. Applied Ergonomics, Vol. 19, No. 4, pgs. 315-318. 2.6 Tables and figures. Tables should not duplicate material shown in figures or vice versa. Each figure and table must be numbered and given a brief caption that adequately explains the information displayed without unnecessary duplication. A reference to each figure or table must be made in the main body of the report, e.g. The results of the survey (see Table 7) show that ..... The layout in Figure 4 indicates ..... For the convenience of the reader, you should put each graph and table as close as possible to the relevant text in the report. 2.7 Appendices are useful for presenting raw data, questionnaire forms, computer programs, theoretical background or any material that is necessary for the reader but does not fit appropriately in the main body of the report. Each appendix should be given a number and a title, included in your list of contents, and referred to in the text, e.g. A computer program was written (see Appendix 2) to ..... 3. WRITING THE REPORT Very few people can write a report by starting at the beginning and just writing straight through to the end. It may help to decide very early on in your project about the major sections (main headings) to be used. Then systematically build up the contents of each section (using sub-sections) as your work progresses. Check that your presentation is in a logical sequence and the sections are coherent. Check that you have done what your introduction says you are going to do, and that your conclusions and recommendations (if any) flow directly from the information presented in the report. The University library contains many books on technical writing. Browse through section 601.49 of library; you could also try 029.6; 378.242; 501.49; 620.00149; and 808.06 e.g. 601.49 G77 Gray, D.E. So you have to write a technical report. 1970 620.00149 M6 Michaelson, H.B. How to write and publish engineering papers and reports, 1982. D. Sculli A.J. Courtney
0
Related docs
Other docs by hongkonguniv