Project and Viva
What the exam tests
The project report and viva check whether you can explain your own work: problem, design decisions, code, testing, limitations and future scope.
Core rules
- Report structure: title, certificate or declaration if required, acknowledgement, contents, introduction, problem statement, objectives, tools used, design, implementation, testing, conclusion, future scope and bibliography.
- Every screenshot should have a caption and be referenced in the text.
- Explain choices: why external CSS, why a particular format, why client-side validation plus server-side checks.
- Keep a testing table: input, expected output, actual output and fix.
- In the viva, demonstrate the working project and be ready to explain any line of code you submitted.
Worked example
Examiner: 'Why did you use external CSS rather than inline styles?' Strong answer: 'The site has two pages sharing typography and layout. One external stylesheet avoids duplication, lets me change the theme in one place, and keeps HTML semantic. Inline styles would raise specificity and make maintenance harder.' Reasoning: the answer ties a technical choice to a project requirement and a trade-off.
Traps
Do not submit a project you cannot explain. Do not claim features you did not build. Do not leave testing until the viva. Do not use vague future scope such as 'make it better'. Do not ignore accessibility or responsive behaviour if the brief asked for them.