Guidelines for Research Student Review Talks and Review Reports

These guidelines are provided on a best-efforts basis.

The aim in both cases is to indicate what you've been doing since you started your degree, or maybe since your previous review.

Headlines: make sure you describe past work, the gap, and your evaluation plans. Further details are below.

What you should have been doing is a mixture of reading, design-type work (which might include what a software engineer would call requirements analysis), implementation, testing, evaluation (by you, of what you have done), and writing-up. How much of each depends on how long you've been going.

When you give a talk, or write a report, for review purposes, some of the things that you need to convince the review panel of are:

This much would be about right for a first review. Subsequently you would proceed to implement your plan:

Back to Review Guidelines
Maintained by Bill Wilson
School of Computer Science and Engineering,
University of New South Wales,
Sydney 2052

Email billw at
Phone: +61 2 9385 6876
Fax: +61 2 9385 4071

Last modified: 18 November 1996