A software engineering final year project is judged differently from a plain programming assignment. Examiners want to see the engineering: clear requirements, a design you can defend, version control, automated tests and a system that survives real use. The idea matters less than how professionally you build it.
Below are 12 FYP ideas for software engineering students in 2026, each chosen because it gives you something meaningful to design, test and document. For a broader mix that includes AI and mobile-friendly web apps, see our 20 best FYP project ideas.
What Examiners Look For in a Software Engineering FYP
- Requirements and scope: a written specification with user stories and clear boundaries.
- Design: architecture diagrams, a database schema and API contracts.
- Process: a Git history with meaningful commits, and an agile or iterative plan.
- Quality: unit and integration tests, plus a test report.
- Delivery: a deployed version and setup documentation.
12 Software Engineering FYP Ideas
1. Code Review Assistant for Pull Requests
Difficulty: Advanced | Timeline: 10–14 weeks
Connect to a Git hosting API, analyse changed files for style, complexity and common bugs, and post structured comments on the pull request.
Tech Stack: Node.js or Python, GitHub API, static analysis libraries
2. Requirements and Traceability Management Tool
Difficulty: Intermediate | Timeline: 8–10 weeks
Store requirements, link them to design items and test cases, and show which requirements are untested. This is a tool your own course teaches, so examiners understand its value.
Tech Stack: Laravel or Django, PostgreSQL, a graph visualisation library
3. Continuous Integration Dashboard
Difficulty: Intermediate | Timeline: 8–10 weeks
Receive webhooks from repositories, run test suites in containers and display build history, failure trends and flaky tests.
Tech Stack: Docker, Node.js, PostgreSQL, WebSockets
4. Feature Flag and A/B Testing Service
Difficulty: Advanced | Timeline: 10–12 weeks
Let developers turn features on for a percentage of users, target segments and view conversion results, with an SDK any app can call.
Tech Stack: Laravel or Node.js, Redis, a small client SDK
5. Technical Debt Tracker
Difficulty: Intermediate | Timeline: 8–10 weeks
Scan a codebase, estimate debt from complexity and duplication metrics, and rank the files most worth refactoring, with a trend over time.
Tech Stack: Python, AST parsing, a web dashboard
6. Automated Test Case Generator from User Stories
Difficulty: Advanced | Timeline: 10–14 weeks
Take structured user stories and acceptance criteria and generate test case outlines that a QA engineer can refine.
Tech Stack: Python, natural language processing libraries, a review UI
7. Microservices Booking Platform
Difficulty: Advanced | Timeline: 12–16 weeks
Split a booking system into users, inventory, payments and notifications services that communicate through an API gateway and a message queue. It demonstrates architecture skills clearly.
Tech Stack: Docker Compose, Node.js or Laravel, RabbitMQ or Redis, PostgreSQL
8. Bug Report Triage System
Difficulty: Intermediate | Timeline: 8–10 weeks
Collect bug reports, detect likely duplicates, suggest severity and route each one to the right team member.
Tech Stack: Laravel or Django, text similarity libraries, MySQL
9. API Documentation and Mocking Platform
Difficulty: Intermediate | Timeline: 8–10 weeks
Import an OpenAPI file, publish readable documentation and spin up a mock server so front-end teams can work before the back end exists.
Tech Stack: Node.js, OpenAPI tooling, React
10. Team Sprint and Velocity Planner
Difficulty: Beginner | Timeline: 6–8 weeks
A lightweight agile board with sprint planning, burndown charts and velocity forecasts. It is achievable and gives you plenty to test.
Tech Stack: Laravel or MERN, MySQL or MongoDB, Chart.js
11. Configuration and Secrets Manager
Difficulty: Advanced | Timeline: 10–12 weeks
Store environment settings and encrypted secrets per project and environment, with role-based access, versioning and an audit log.
Tech Stack: Laravel or Node.js, encryption libraries, PostgreSQL
12. Mobile-First Progressive Web App for Campus Services
Difficulty: Intermediate | Timeline: 8–12 weeks
Timetables, notices, lost and found and event sign-up in one installable app that works offline for read-only content.
Tech Stack: React or Vue, service workers, a Laravel or Node.js API
Documents and Evidence to Prepare
- Software requirements specification
- Architecture and database diagrams
- Test plan, test cases and results
- User manual and deployment guide
- A short demo script for the viva
Our guide to choosing an FYP title and writing the proposal shows how to turn any of these ideas into an approved proposal.
FAQ: FYP for Software Engineering Students
What makes a software engineering FYP different from a computer science FYP?
Software engineering projects are marked heavily on process and quality: requirements, design, testing and documentation. Computer science projects often weigh algorithms and research novelty more. Ask your supervisor which criteria carry the most marks.
Do I need to build a mobile app for my software engineering FYP?
No. A well-engineered web application, API or developer tool is fully acceptable. A progressive web app gives you mobile access without maintaining two native codebases.
How important is testing in a software engineering FYP?
Very important. Automated unit and integration tests, a test report and evidence of bugs found and fixed are among the clearest ways to show engineering discipline.
Can I work in a team on my FYP?
Many universities allow teams of two to four. If you do, use Git branches, pull requests and issue tracking, and record who built what, because each member is usually assessed individually.
Want Expert Help?
YourSiteFactory can help with architecture reviews, code, testing and documentation. See the FYP student offer or get a free quote.
