These are starting points. Don't copy one word for word and submit it. Your department may already have three projects with the same title, and your supervisor will want to see that you thought about it. Pick one that fits the tools you know, narrow it to a real place or group, and check the past projects in your department before you submit.

Most of these are written in the "design and implementation of" shape that computer science departments in Nigeria tend to use. Each comes with a short note on what it needs, because the hardest part of a CS project is usually getting data or users to test with, not the code.

If you haven't settled on how to choose yet, read how to choose a final year project topic first.

Systems for your own university

These are popular for a reason. You understand the problem, the users are around you, and you can test with real students.

  1. Design and implementation of an online hostel allocation system. Needs the allocation rules from student affairs, even if you simplify them.
  2. Design and implementation of a course registration clash detector. Takes a timetable and a list of courses and flags clashes. You need one department's real timetable.
  3. A lecture venue booking system for a faculty. Small, clear scope, and easy to demo.
  4. Design and implementation of a past question bank with course code search. Needs a few dozen scanned past questions to make the demo believable.
  5. An online clearance system for final year students. Model the offices a student visits and let each one sign off.
  6. A student complaint and feedback system for a department. Include anonymous submission and a dashboard for the head of department's office.
  7. Design and implementation of a project supervisor allocation system. Matches students to supervisors by area of interest and supervisor load.
  8. A lost and found system for a university campus. Simple to build, so put the effort into search and matching.

Web and mobile apps

  1. Design and implementation of a mobile app for campus shuttle schedules. You'll have to collect the routes and times yourself.
  2. A marketplace app for students to buy and sell used textbooks. Focus on listing, search and messaging. Skip payments unless your supervisor asks.
  3. An offline-first note-taking app that syncs when a connection is available. A good fit for anyone interested in how apps handle poor network.
  4. A web-based inventory system for a small pharmacy. Find a real pharmacy near campus willing to tell you how they track stock.
  5. A queue management system for a hospital outpatient clinic. Needs a clinic's actual process, so visit the university health centre.
  6. Design and implementation of an appointment booking system for a barbing or hair salon. Easy to test with a real business.
  7. A church or mosque membership and attendance management system. Very buildable. Make it interesting with reports and SMS reminders.

Machine learning and data

These need data you can get. Check that before anything else.

  1. Prediction of student academic performance using machine learning. You need anonymised results data. Ask your department early, because approval takes time.
  2. Sentiment analysis of tweets about a Nigerian topic. Pick a narrow topic, like a fuel price change. Collecting tweets is harder than it used to be, so look for an existing dataset.
  3. Detection of fake news headlines in Nigerian online newspapers. You'll label data yourself, so keep the dataset small and the labels clear.
  4. Crop disease detection from leaf images. Public datasets exist for cassava and maize. Good if you want to work with image classification.
  5. Spam SMS detection using naive Bayes. A classic, well documented, and easy to explain in a defence.
  6. Handwritten digit recognition for scanned answer sheets. Train on a public dataset, then test on a few sheets you scan yourself.
  7. A recommender system for elective courses based on past student choices. Needs registration data, so the same caution as the first topic in this section.
  8. Customer churn prediction for a mobile network subscriber dataset. Public telecom churn datasets are available. Explain why your features matter, not just your accuracy.

Security

  1. Design and implementation of a two-factor authentication system for a student portal. Build the login flow and show it working with one-time codes.
  2. A phishing website detection tool using URL features. Public datasets of phishing URLs are easy to find.
  3. An intrusion detection system using machine learning on network traffic data. Use a public dataset. Don't try to collect live traffic.
  4. A file encryption tool comparing AES and another cipher. Measure speed and file size so chapter four has numbers.
  5. A password strength checker with feedback for users. Small, so add a survey of how students actually choose passwords.
  6. Steganography: hiding text in images. Explain the method clearly and measure how much the image changes.

Networks and hardware

These need parts. Budget for them before you commit.

  1. Design and implementation of a smart attendance system using RFID. Needs an RFID reader and cards. Cheap, and the demo is satisfying.
  2. An IoT-based room temperature and humidity monitor. A microcontroller and a sensor are enough.
  3. A water tank level monitor with SMS alerts. Hostels and homes both have the problem, so you'll have a ready story for why it matters.
  4. A campus Wi-Fi coverage map from signal readings. You walk around and measure, so it's legwork more than code.
  5. Design and implementation of a smart energy meter monitor. Talk to someone who has done electronics before you buy anything.
  6. Performance comparison of two routing protocols in a simulated network. Done entirely in a simulator, so no hardware cost.

Software engineering and other areas

  1. Comparative analysis of two web frameworks for building the same app. Build a small app twice and compare speed, code size and effort.
  2. Automated testing of a web application. Pick an open source app and write a test suite for it.
  3. A Yoruba, Hausa or Igbo to English dictionary app with audio. Needs a speaker to record pronunciations. Very good for a strong "significance of the study".
  4. A chatbot that answers questions about a department's handbook. Keep the knowledge to one document so you can test it properly.
  5. An e-voting system for student union elections. Pay attention to how one student is stopped from voting twice.
  6. Design and implementation of a result computation system with GPA and CGPA. Needs your department's grading rules exactly right.
  7. A timetable generator for a department using a genetic algorithm. Hard, but well regarded if you get it working.

Before you take one to your supervisor

Narrow it first. "An e-voting system" is a starting point. "An e-voting system for departmental elections with one vote per matric number" is a topic. Then write a short paragraph on what you'll build, what you'll test it with, and why it matters to someone.

When it's approved, how to structure a final year project, chapter by chapter covers what goes into each chapter, including how chapter three changes for a system you build.