Practical Work and Project
What this domain tests
Practical Work and Project tests lab skills: writing and running Python programs, SQL queries, HTML pages, documenting algorithms, testing and explaining your project in a viva.
Core rules
- A practical record should show problem statement, algorithm/pseudocode, code, test data, output and conclusion.
- Python practicals commonly cover input/output, conditionals, loops, functions, lists, strings, dictionaries, file handling and exception handling.
- SQL practicals require creating tables with appropriate data types and constraints, inserting rows, and writing SELECT queries.
- HTML practicals require a valid structure, headings, lists, links, images, tables and a form.
- A project needs a clear scope, modules, data storage, validation, test cases and a user guide. Keep source files and a backup.
Worked example
A student record project stores roll number, name and marks in a CSV file. Menu: 1 Add, 2 Display, 3 Search, 4 Exit. add() takes input, validates marks as 0–100, appends a line roll,name,marks; display() reads and prints rows; search() compares the roll number. Test case: add (1, "Asha", 87), search 1 → found; search 2 → "Not found". Reasoning: each function has one job; validation prevents bad data; a test case checks both a hit and a miss.
Traps
Do not submit code you cannot explain. Hard-coded file paths fail on another machine. Missing validation allows impossible marks. A program that runs once may still fail on empty input. Back up the project and keep output screenshots or logs.