I'm a third-year software engineering student, and I need to build, document, and test an independent project for my final-year assessment. It makes up about 40% of my grade, so I want to choose something worthwhile rather than rush into a generic app.
I already have experience with several technologies and personal projects. One of my larger projects is a basic Vim-style text editor written in C++, including custom commands. I've considered expanding it with features that the standard editor does not provide out of the box, such as a file tree, built-in syntax highlighting, or other tools that could make coding more convenient.
I also have experience developing full-stack applications with React, React Native, and Flutter, as well as working on NLP and machine-learning projects in Python. However, most of these ideas are based on existing concepts, so I'm unsure whether improving one of them would be substantial enough for a year-long final project.
I could build a typical CRUD application and add an AI feature, but that feels unoriginal and not especially meaningful. Do final-year projects need to solve a completely new problem, or can extending and evaluating an existing tool be a strong choice? If you've been in a similar situation, how did you narrow down your idea and decide what was worth pursuing?
4 Answers
Look for repeated frustrations in your own life or workflow. Think of times you wished a tool could automate a tedious task or handle a process more conveniently. That can lead to a much better project than starting with a technology buzzword. Your editor is also a promising direction because you already understand its codebase and can build a focused improvement on top of it.
You may be putting too much pressure on the originality requirement. A final project usually needs to demonstrate that you can design, implement, document, and test a software system—not necessarily create something the world has never seen. Even a fairly ordinary application can be a good submission if the engineering is solid and the scope is appropriate. Your existing experience suggests you’re capable of doing well; choose something you can finish and evaluate thoroughly rather than chasing an impressive-sounding idea.
Your custom Vim-style editor is already a strong foundation. You don’t need to invent an entirely new category of software; you could define a specific problem that existing editors handle poorly and build around that. A file navigator, language support, debugging workflow, project management features, or better accessibility could all become meaningful additions if you clearly explain the design, implement them properly, and test whether they help users. The important part is to set a realistic scope and evaluate the result instead of simply adding random features.
It can be, as long as the project is framed around a clear goal. Compare your tool with existing editors, identify a genuine limitation or target audience, and measure things such as performance, usability, or productivity. That gives you plenty to document and test beyond just writing more code.
If you want the project to become a serious product, choose a problem first and then decide which technologies actually help solve it. A security-training platform that simulates defensive and offensive scenarios, for example, could combine software engineering, automation, and machine learning. Just be careful with the scope and keep all testing inside controlled, authorized environments. A focused, demonstrable system is more valuable than trying to combine every trendy technology at once.
That’s what I was wondering about. The editor is already functional because I started it near the end of my second year, so I’m unsure whether adding features would be enough to justify working on it for the full year.