Most final year students don't struggle with the writing. They struggle with the topic. A topic that sounded clever in September turns into a problem in January, when the data won't come, the scope is too wide, or the supervisor sends it back for the third time.
Workable topics have a few things in common, and you can check for them before you submit.
Start with the data you can actually get
Before you fall in love with a topic, ask one question: where will the data come from?
If your project needs questionnaires, you need people who will fill them. Students in your own faculty are easy to reach. Staff of a federal ministry in Abuja are not. If your project needs records, you need someone willing to give you those records. Hospitals, banks and government offices often say no, or say yes and then take months.
For a project you build, like most computer science and engineering projects, the question changes slightly. Can you build it with tools you already know, on the laptop you already have, in the time you have? A face recognition attendance system sounds good until you find out you need a GPU and a few thousand labelled photos.
Pick the topic whose data you can see from where you're standing.
Cut it down until it fits in one semester
Supervisors reject broad topics more than anything else. "Social media and Nigerian youth" is a whole subject area, and nobody can study all Nigerian youth in one semester.
You make a topic smaller by fixing three things: who, where and what exactly.
- Effect of social media on students
- Use of WhatsApp for academic information among undergraduates
- Use of WhatsApp class groups for academic information among 300 level students of a Nigerian university
Each step adds a limit. The third version tells your supervisor who you'll survey, what you'll ask about, and roughly how big the job is. That's what they want to see.
The same works for building projects:
- An e-learning system
- Design and implementation of a past question bank with course code search for a university department
Find out what has been done before
Your department almost certainly keeps bound copies of past projects, usually in the departmental library or the project coordinator's office. Spend an afternoon there before you submit anything.
Read the titles and abstracts from the last three or four years. You're looking for two things. First, topics that are already taken, because a copy of a recent project will get rejected. Second, topics you can extend. A study done on 200 level students in 2019 can be done on 400 level students now, or in a different faculty, or with a different method. Extending an old project is normal, and supervisors know it.
Ask final year students from last session what topics got approved and which ones were sent back. They know what your lecturers like.
Write the title the way your department writes them
Project titles in Nigerian universities tend to follow a few patterns. Using the familiar one makes your topic look serious at a glance.
- Assessment of X among Y
- Impact of X on Y: a study of Z
- Factors affecting X in Y
- Design and implementation of a system that does X for Y
Look at the approved titles from your department and copy their shape. If every title in the cabinet starts with "Design and implementation of", yours should too.
Submit more than one topic, and make them different
Many departments ask you to submit two or three proposed topics, and the supervisor or project committee picks one. Don't submit three versions of the same idea. If the first one gets rejected for lack of data, the other two will fail for the same reason.
Make your options different in a useful way: one survey-based topic, one using records or secondary data, and one that's a little more ambitious. That way at least one is likely to survive.
Go to your supervisor prepared
When you meet your supervisor, bring a short paragraph for each topic. Three or four sentences are enough:
- What the problem is, in one sentence.
- What you will do about it.
- Where your data or materials will come from.
- Why it matters to someone, whether that's students, a business or your department.
Supervisors are busy. A student who arrives with a clear paragraph gets a clear answer. A student who arrives with "I'm thinking of something on cybersecurity" gets told to come back.
Why topics get rejected
The same reasons come up every year. The topic covers a whole country, a whole industry or "students" in general. The study depends on people or records the student can't reach. It repeats a recent project in the department without changing anything. It belongs to another department, like a mass communication topic that is really political science. Or the title leans on words like "technology" and "development" without saying which technology or what kind of development.
A final check before you submit
Read your topic out loud and answer these honestly:
- Can I say in one sentence what I'm going to find out or build?
- Do I know exactly who or what I'm studying, and where?
- Can I get the data or build the thing before the deadline?
- Has this exact topic been done in my department in the last few years?
- Would my supervisor understand it without me explaining?
If you can answer all five, you have a topic.
Once it's approved, the next job is the outline. How to structure a final year project, chapter by chapter walks through what goes in each chapter. If you're in computer science and still looking for ideas, start with the list of computer science project topics.
