Final Year Project Proposal Best Practices

Chapter 1 of 8 · 4 practices · 4 min · 3-question quiz

Choose an idea worth a year of your time

A good final year project starts from a real problem your team can understand, build for and evaluate. Pick the problem before you pick the technology.

Start: Start from a real problem that real people have

4 practices in this chapter

  1. 1Start from a real problem that real people haveThe strongest proposals begin with a sentence like "Small pharmacies in our area track expiry dates on paper and throw away stock every month", not "We want to build an app using Flutter and…
  2. 2Match the idea to what your team can learn in the time you haveA final year project should stretch you, but it has to finish. List what the idea needs (for example a mobile client, a backend API, a trained model, an embedded device) and compare it honestly with…
  3. 3Check what already exists before you commitCommittees reject proposals that duplicate an existing product or a previous year's project without adding anything. Spend an evening searching before you decide: Products: search app stores and the…
  4. 4Decide whether it is a development project or a research projectMany departments recognise two kinds of final year project, and they are judged differently. The FAST School of Computing handbook, for example, separates development FYPs from R&D-based FYPs and…

Check yourself on this chapter

3 questions, right here once you are signed in. Your progress is saved as you read.

Sign up for the quiz