Your TM470 project can be about pretty much anything, providing that it
- has a significant computing component, and
- allows you to draw on your earlier level studies to enable you to demonstrate and to further develop your knowledge and skills.
Drawing on a point that I share in my introductory tutorials, your project should address a non-trivial question and one that is reasonably difficult without an obvious answer; you should have a problem that needs a solution.
Projects can also be:
- Development projects – you create something.
- Research projects – you find something out.
- Evaluation projects – you do comparison, or test something out.
Typically, your project will have elements of each of these projects.
Your title that you choose should reflect the aims and objectives of your project. It should ideally suggest whether it is development, research or evaluation project. Your project title should also be concise. If it is more than ten words, you might want to think of how to simplify it. You need something that is concise, and prepares your examiner for what they will encounter.
Here are some titles of projects that have been inspired from the various projects that I have seen over the years:
- Knowledge management system for field engineers
- Web application for management of school transportation
- An app to help a restaurant to buy organic produce
- Web application for selling of art to art galleries
- An accessibility evaluation of museums in a city
- Development of a test automation framework for a company
- An app used to provide information and guidance to carers
- Financial reporting app for a market trader
- Rugby club, soccer club or cycling club management tool
- A legal case management system
- An app used to recommend reading resources to parents
- Evaluating the potential effectiveness of a new network architecture
Returning to the earlier point, your project should solve a problem that is non-trivial.
Acknowledgements
Thanks are extended to fellow tutor Karl Wilcox who inspired some of my tutorial slides, which may well have influenced this post. I now have no idea which are his words, and which are mine. I think Karl made the very useful point that your project needs to be both significant and non-trivial. These two points clearly stuck with me.