Project Work and Viva Voce
What this domain tests
Whether you can plan, execute, document and defend a small IT/ITeS project - the report is marked for structure and evidence, the viva for understanding.
Core concepts
- Report structure: title page, certificate, acknowledgement, index, introduction, objectives, scope, methodology, tools used, work done (with screenshots/tables), findings, limitations, conclusion, bibliography.
- Objectives must be measurable ('to design a spreadsheet that records 50 stationery items and generates a monthly stock report'), not vague.
- Evidence: data-entry logs, spreadsheet formulas, screenshots of forms, call/transaction samples with personal data masked.
- Viva preparation: be able to explain every formula, every design choice and every number in your own report.
- Ethics: no copied project, cite sources, mask real customer data, do not present a downloaded template as your own build.
Worked example
Project title: 'Data entry and stock reporting for a neighbourhood stationery shop'. Reasoning: the objective is measurable, the data source is real and permitted, the tool is a spreadsheet with a validated entry sheet and a pivot-style summary, the evidence is the formula sheet and monthly report screenshots, and the limitation is that stock counts were manual. Every element answers a likely viva question before it is asked.
Traps that cost marks
- Submitting a report with no methodology section, so the examiner cannot see what you did.
- Screenshots with a classmate's name or a client's real phone number visible.
- Being unable to explain a formula in your own file - the strongest signal of copied work.
- A bibliography that lists websites but no access dates.