M.Sc. Project Requirements
The project work is intended to be equivalent to two courses or two man-months of effort. It is up to you and your supervisor to determine whether you have performed adequate work for the project.
The written project report may be thought of as a small-scale version of a M.Sc. thesis. It must be typewritten and length would typically range between 20 and 30 double-spaced pages. Program listings should only be attached as appendices. It should include an adequate introduction to the topic, as well as a full description of the work you have performed. While such depth of scholarship as for a thesis is not required, you must demonstrate you are familiar with state-of-the-art methods in the area of your project topic. A typical project involves the implementation of an interesting algorithm, program or system. A mundane data processing problem with well-known implementation techniques would probably not be suitable for a project. Alternative project formats, such as a research survey or analysis of a problem, are equally acceptable.
It is permissible to submit a project for which an outside employer has paid you. This must satisfy all the conditions given above for a project. In addition, you must supply written permission from the outside employer that the work may be used in this way. In particular, the employer must surrender any proprietary interest in the project report; the report becomes the property of the School and is subject to the University research and patent policies, as described in the Faculty of Graduate and Postdoctoral Studies General Information, Regulations and Research Guidelines. Your supervisor must be a faculty member in the School, and you must prove to his/her satisfaction that the project is solely your work.
The suitability of your written report is determined by your project supervisor.
Report and Abstract Guidelines
The abstract is to appear on a single, separate (loose) page. It is to contain the names of the student and supervisor, title of the project, date, and a brief description (suitable for a general computer science audience) of the work.
The project report should be a substantial document, containing a complete description of the work done, in clear, correct English or French. It should include a non-technical over-view, specification and technical background for the project, description of the algorithm or design used, implementation details, documentation, a user's guide and a bibliography. Depending on the nature of the project, some of the preceding items may not apply and other items may need to be added; for example, most project reports will require appendices of program listings in order to provide a complete description of the project.
You must obtain the signature of the supervisor on the report to indicate that it has been accepted. You then file a copy of the signed project report, with an abstract (on a separate page) with the graduate secretary. She will then submit this to the Technical Reports Librarian, who assigns a number to the report and abstract, and both are kept on file. A compendium of abstracts and their numbers are available in the department. Anyone who wishes to view a project report can make arrangements with the Technical Reports Librarian to do so.