Your FYP shapes your last year at university: the skills you graduate with, a big part of your marks, and often the first thing an interviewer asks about. This guide walks through choosing a good FYP in six steps, with a scoring sheet to compare ideas, a two-semester plan and what panels look for.
If you only need ideas, start with our 70 FYP ideas for computer science students or the FYP idea generator, then come back here to pick between them.
Step 1: Start from the job you want
Choose the job first and the project second. Your FYP is the biggest piece of work on your CV, so it should prove the skills that job needs.
- Web or mobile developer: a complete product with login, a database and a real deployment
- Data or machine learning: a project with a real dataset, a baseline and an honest evaluation
- Embedded or IoT: hardware that works reliably in a live demo
- IT or business systems: a system a real organisation uses, with roles and reports
- Research or an MS later: a clear research question and results you could write up as a paper
Step 2: Build the right group
Two or three people with different strengths beat three people with the same one. Agree on roles before you agree on an idea: who leads the backend, the front end or mobile app, and the model or hardware. Share the documentation instead of leaving it to one person.
Use Git from the first week and agree on a weekly meeting time. If a member goes quiet, the commit history and meeting notes show who did what, which protects everyone at the viva.
Step 3: Collect five to ten candidate ideas
Good FYP ideas usually come from one of these places:
- A problem you have seen up close: a family business, your hostel, your department office
- Your supervisor’s research area, which also makes supervision easier
- Last year’s FYP expo: pick a project and improve one clear weakness, rather than copying it
- Open datasets or APIs that make an interesting question possible
- Idea lists by field: AI, software engineering, IT, cyber security, data science, web development, mobile apps, Python, computer engineering and IoT, and business (BBA)
Step 4: Score every idea
Give each idea a score from 1 to 5 on the six questions below, as a group, and add them up. The highest total wins. If two ideas tie, choose the one whose data or hardware is easier to get.
| Question | What a 5 looks like |
|---|---|
| Is there a real user? | You can name a person or business who would use it and test it |
| Can you get what you need? | The data, hardware or APIs are available today, not “we’ll find them later” |
| Does it fit two semesters? | One core feature can work end to end by the mid-term evaluation |
| Can your group build it? | You know the stack, or can learn it within a month |
| What is new about it? | You can say in one sentence how it differs from existing apps and past FYPs |
| Does it help your career? | It builds the skills for the job you chose in step 1 |
Step 5: Find a supervisor and pitch well
Read faculty profiles and match your top idea to someone’s interests. Ask early, because the best supervisors fill up first. Send a short message, not a long proposal:
“Dear Dr. [name], we are a group of three BSCS students planning our FYP. We want to build [one sentence: what it does, for whom]. It fits your work on [their area]. Our plan is [approach in one line], and our group has experience with [skills]. Could we meet for ten minutes this week to get your advice?”
Take your scoring sheet to the meeting. Supervisors respond well to groups that have already thought about data, scope and risks.
Step 6: Cut the scope before the proposal
Write your project in one sentence: “[Name] helps [user] do [task] by [approach].” If you cannot, the idea is still too vague.
Then sort every feature into must have, should have and could have. Put only the must-haves in your proposal and list the rest as future work. Panels reward a smaller system that works over a big one that half works. Our FYP proposal format shows what each section needs.
A two-semester plan
Adjust the weeks to your department’s calendar.
| When | What to finish |
|---|---|
| Semester 1, weeks 1 to 3 | Group, idea scoring, supervisor |
| Semester 1, weeks 4 to 6 | Proposal and proposal defence |
| Semester 1, weeks 7 to 12 | Requirements (SRS), design and the data or parts |
| Semester 1, weeks 13 to 16 | A working prototype of the core feature for the mid-term evaluation |
| Semester 2, weeks 1 to 6 | The remaining must-have features |
| Semester 2, weeks 7 to 10 | Testing with real users, fixes and results |
| Semester 2, weeks 11 to 13 | Report and documentation |
| Semester 2, weeks 14 to 16 | Final demo, a backup demo video and viva preparation |
What panels look for
- A clear problem and a real user, stated in the first minute
- A live demo of the core feature that works the first time
- Evidence: test results, accuracy, time saved or user feedback
- Every member able to explain their own part, and the code behind it
- A report and diagrams that match the system you actually built
How to make your FYP better if you have already chosen
- Put it in front of five real users and change one thing based on what they say
- Measure something: accuracy, response time under load, or time saved
- Deploy it on a real server or publish a test build, instead of running it only on a laptop
- Pick one hard part (a solver, sync, security, a model) and do it properly
- Record a demo video in case the live demo fails on the day
Ideas to avoid
- Forms and tables with no real user and nothing hard in them
- Ideas that depend on data you do not have permission to use
- Hardware that cannot arrive and be tested before the mid-term
- Scope that is too broad, like “an app for all of Pakistan”
- A copy of a well-known app with nothing new
- Paid APIs with no budget or free tier for the demo
Picked an idea but the deadline is close?
Ezitech builds final year projects — Rs 25,000, delivered in 3 days. Tell us the idea you have chosen and your supervisor’s requirements, and we will tell you honestly whether it fits.
Frequently asked questions
Can we change our FYP idea after the proposal?
Usually only with your supervisor’s approval, and the later you change, the more it costs you. If an idea is failing, raise it early and try to stay in the same domain so your proposal work still counts.
Should we choose an AI FYP?
Only if you have the data and it fits the job you want. A well-built web or mobile system with real users often scores better than a weak model trained on a downloaded dataset.
Is a research FYP better than a development FYP?
Choose research if you plan to do an MS or PhD, and development if you plan to join industry. Both can earn top marks when they are done well.
How do we name our project?
Use a name that says what it does, plus an optional short brand name. See 60 FYP title examples.
Next steps
Browse ideas by field: 70 CS ideas · AI · software engineering · IT · cyber security · data science · web development · mobile apps · Python · computer engineering (IoT) · business (BBA). Need money to build it? See FYP funding in Pakistan.