Choosing an IT FYP scope
Pick a scope that you can design, build, test and document in the time available. A realistic IT FYP has a clear problem, a defined set of features, a small group of users and a way to evaluate the result.
Avoid trying to build "a complete platform". Choose the core function, such as a booking workflow or a prediction model, and treat other features as future work. Check that you have the required hardware, software licences and data.
Web and mobile ideas
Web and mobile ideas:
- A web-based booking system for a small clinic or salon.
- A mobile app that helps students track their study tasks.
- An inventory management system for a campus club or shop.
- A lost-and-found portal for a university.
- A job-matching platform for part-time student work.
Include user requirements gathered from real users, usability testing and security basics such as authentication and input validation.
AI and machine learning ideas
AI and machine learning ideas:
- Sentiment analysis of social media posts about a local brand.
- An image classifier for plant disease detection.
- A recommendation system for university courses.
- Predicting student dropout risk from anonymised data.
- A chatbot for answering frequent student questions.
You need a suitable dataset, a baseline for comparison and proper evaluation metrics such as accuracy, precision, recall or F1. Document your data source and cleaning steps and consider privacy and bias.
Data and analytics ideas
Data and analytics ideas:
- A dashboard visualising sales or campus facility usage.
- Forecasting electricity usage from historical data.
- Analysing customer reviews to find common complaints.
- Data quality assessment for a public dataset.
- Comparing prediction models for house prices.
Use open datasets, such as government or Kaggle datasets, or data you collect with permission. Explain your analysis steps and interpret the results for decision-makers.
Project methodology (Agile, Waterfall)
Agile develops the system in short cycles (sprints), with feedback after each one. It works well when requirements may change. Waterfall moves through fixed stages (requirements, design, implementation, testing, deployment) in order, which suits well-defined projects.
Choose the one that fits your project and explain why. Many FYPs use a light Agile approach with weekly iterations and a backlog of features. Whichever you choose, show the plan, deliverables and testing in the report.
Documentation and demo tips
Keep documentation in step with the build. Include requirements, use cases, system architecture, database design, key screenshots, test cases and results, and a user guide.
For the demo, prepare a short scripted walkthrough of the main user journey, use realistic test data and have a backup recording in case of network or software failure. Practise explaining your design choices and what the system cannot do.