Questions and answers
Tell us about your project in two minutes.
Problem in one line, your solution in two lines, how it works in three steps, and the result. Practise this until it takes under two minutes.
Why did you choose this topic?
Connect it to a real observation: a college process, a local problem, your internship, or a gap in a paper you read.
What is the difference between the existing system and yours?
Name one existing system and state two concrete differences such as cost, accuracy, speed or a feature.
Explain the system architecture.
Walk through the diagram from user or input to output. Mention where data is stored and how modules communicate.
What was your contribution in the group?
Be specific: “I built the admin module and the database schema and wrote the testing chapter.”
Why this technology and not another?
Give reasons tied to the project: library support, hardware limits, deployment, team skill. Mention one alternative.
Which SDLC model did you follow?
Most student projects follow an iterative or agile approach: small builds reviewed weekly by the guide. Say what you actually did.
How did you test the project?
Mention unit testing of modules, integration testing, and show two or three test cases with results.
What problems did you face?
Pick one technical problem and explain how you debugged it. Examiners like a real story.
What are the limitations?
Two honest limits. Admitting them shows understanding.
What is the future scope?
Two specific extensions that follow from the limitations.
How is your database designed?
Name the main tables, primary and foreign keys, and the normal form.
Is your project secure?
Mention password hashing, input validation, role-based access, or for hardware, fail-safe behaviour.
What did you learn?
One technical skill and one teamwork or planning lesson.
Can this be used commercially?
Say who the user would be and what would need to improve first.
Viva day checklist
- Project runs on your own laptop without internet if possible
- Backup on a pen drive and a recorded demo video
- Black book with all signatures
- PPT opened and tested on the projector
- Each member knows the whole flow, not only their module
If you do not know an answer
Say what you do know and where you would look: “I have not implemented that, but I understand it would need…”. Guessing confidently is worse than an honest partial answer.
FAQs
How long does a project viva last?
Usually 15 to 25 minutes per group: about 8 to 10 minutes of presentation and demo, then questions.
Do examiners ask questions outside the project?
Yes, often basics of the subject your project uses: DBMS, OOP, networking, electronics or design principles.
How can I prepare if someone else helped build my project?
Get a full walkthrough of the code or design, redo one small feature yourself, and practise explaining every diagram. Our viva sessions are built for exactly this.
Last reviewed: 2026-10-11. Always follow the format your own department gives you.