Plan, write and defend your software engineering diploma project.
Practical guides for final-year students: how to pick a topic, structure the thesis, evaluate your system and prepare for the defence. Free, no sign-up.
Browse topic ideas Thesis structureTopic ideas
A good diploma topic has a clear problem, a system you can actually build, and a way to measure the result. Examples by area:
Platforms and APIs
- A booking or scheduling service for a small organisation
- A REST/GraphQL API gateway with rate limiting
- Role-based access for a university portal
Analytics and storage
- A dashboard for learning-progress statistics
- Comparing relational and document databases on a real workload
- A recommendation module for course selection
Infrastructure and DevOps
- A CI/CD pipeline for a student project
- Centralised logging and monitoring for a small cluster
- Backup and recovery strategy with measured recovery time
Authentication and privacy
- Single sign-on with multi-factor authentication
- Audit trail for changes to academic records
- Threat model of a web application
Apps
- A cross-platform app for campus navigation
- Offline-first notes with synchronisation
- Push-notification strategy and its effect on retention
Emerging technology
- Blockchain-based records and their trade-offs
- Machine-learning assisted code review
- Energy use of container orchestration
Recommended thesis structure
Requirements differ between universities, so always check your department's template. This outline works as a starting point; the shares are typical, not rules.
| Chapter | Typical share | What it covers |
|---|---|---|
| Introduction | 5-8% | Problem, goals, scope, and the questions the work answers. |
| Background | 15-20% | Existing solutions, technologies, and why the chosen approach fits. |
| Requirements and design | 20-25% | Functional and non-functional requirements, architecture, data model. |
| Implementation | 20-25% | Key decisions, interesting code paths, and problems you solved. |
| Testing and evaluation | 15-20% | Test strategy, measurements, comparison with the goals. |
| Conclusion | 5-8% | Results, limitations, and ideas for further work. |
Defence checklist
Things reviewers usually look for. Tick them off a week before the date.
- The goal in the introduction matches the conclusion, point by point.
- Every requirement is either met, partly met or explicitly out of scope.
- Results are backed by numbers, tests or a demonstration, not by opinion.
- Sources are cited consistently in the style your department requires.
- The demo works offline or has a recorded fallback.
- The talk fits the time limit and you rehearsed it aloud at least twice.
FAQ
How long should a diploma project take?
Most programmes allow one to two semesters. Plan the first month for topic and literature, and keep the last month for testing, writing and rehearsal.
Do I need to build a working system?
For software engineering programmes, usually yes, or at least a working prototype with a clear evaluation. Check with your supervisor.
Can I reuse code from open-source projects?
Yes, if the licence allows it and you state clearly which parts are yours and which are reused.
Do you write theses for students?
No. This site only publishes guides. The work you hand in has to be your own.