The following is a general template for a masters project proposal under my supervision, and therefore, software based.

  • Title
  • Disclaimer (stating your own work etc. - usual plagiarism requirements)
  • Abstract
  • Acknowledgements (optional)
  • Contents
  • Chapter 1 - Introduction
    • State the problem you are trying to solve
    • Why is it worth tackling?
    • What approaches are available (briefly)?
    • What approach have you chosen?
    • Any special knowledge you presume of the reader to understand the proposal.
    • Any special typography or terminology (if too many use a glossary).
    • A "road map" of the proposal document ... "In Chapter Two we describe xxxx. In Chapter Three we describe yyyy..."
  • Chapter 2 - Background
    • Any information the reader requires in terms of techniques/technology that isn't part of the programme you have studied.
  • Chapter 3 - Analysis, Requirements, and Design
    • What it says on the title
    • Should include appropriate formal design diagrams/notation as necessary
    • Any language selection, libraries, frameworks, etc., and why you have selected them.
    • If you've written some code then discuss this briefly and how this will impact the final work.
  • Chapter 4 - Experimentation & Evaluation
    • Again, what it says on the tin!
    • Briefly describe how you are going to show that your work meets the original aims and objectives; this doesn't mean just testing the code!
  • Chapter 6 - Timescale
    • Provide a GANTT chart which shows the timeline for your work. Probably a topic, rather than week-by-week, view will be most useful to the examiners.

Now, "one size does not fit all" - this structure is meant to be a starting point; you may have more, or less, chapters. Be flexible and check with me about what you are writing.

I prefer to see the proposal a section at a time (or even just a few pages at the start). A whole proposal sent to me to read at the end, with no chapters submitted prior to that, is a recipe for problems. It really doesn't give me any time to say, "No, change the style", or "No, I suggest you do it this way".