Punjab PSEB SS Computer Science common mistakes
Punjab PSEB SS Computer Science · Understand the traps and how to avoid them.
Writing code answers without declaring variables or with undeclared variables, so the logic is correct but the program would not compile or run.
Students memorise the algorithm in pseudocode form and skip the declaration lines, forgetting that PSEB theory papers require syntactically complete programs with data types, semicolons and the main() function.
What to do instead
Before writing any program answer, draft the variable list with types on rough work, then transcribe the full program with declarations, headers and closing braces. Practise writing ten short programs (sum, factorial, largest of three, prime check) from memory with complete syntax each time.
Confusing the assignment operator '=' with the equality operator '==' inside if and loop conditions.
In mathematics '=' means equality, and beginners read conditions aloud as English ('if x equals 5') while typing a single '='. Compilers often accept it silently in C/C++, so the error is never seen during practice.
What to do instead
Adopt a reading rule: in any condition, say 'is equal to' and type '=='. After writing each condition, circle every '=' and confirm whether it is inside a condition (needs '==') or a statement (needs '='). Include two deliberately wrong conditions in revision notes and explain the output difference.
Off-by-one errors in loops: writing for(i=1;i<n;i++) when n items must be processed, or using <= with an array index that runs to n.
Students mix 1-based counting from maths with 0-based array indexing, and they do not trace the loop on paper. The boundary cases (first and last iteration) are never checked.
What to do instead
For every loop, write a trace table with columns for iteration number, loop variable value and output, and run it for n=1, n=2 and n=3. State explicitly whether the loop is 0-based (arrays, use <n) or 1-based (counting, use <=n).
Describing the fetch-decode-execute cycle or CPU components in vague generalities ('the CPU processes data') instead of naming registers and buses.
This topic is taught as a narrative and students revise the story rather than the terminology, so they cannot recall PC, MAR, MBR, IR, ALU, control unit, address bus and data bus under exam pressure.
What to do instead
Build a one-page diagram of the CPU with each register labelled and a one-line function. Write the cycle as numbered steps naming the register involved at each step (PC to MAR, memory to MBR, MBR to IR, decode, execute). Recite the steps aloud until the register names come without prompting.
Mixing up number-system conversions, especially decimal-to-binary fractional values and hexadecimal grouping, producing answers that are wrong in the last digit.
Students learn only the integer division method and then guess at fractions, and they group bits from the wrong end when converting binary to hexadecimal.
What to do instead
Practise the two separate methods: repeated division by the base for integer parts, repeated multiplication by the base for fractional parts. For binary to hex, always pad the binary number on the left to a multiple of four bits, then group from the right. Do five conversions each way and verify by converting the answer back.
Writing SQL queries that select all columns with SELECT * when a specific column list is asked, or omitting the WHERE clause so aggregate results cover the whole table.
Students copy the pattern from textbook examples without reading the question's requirement, and they do not distinguish row filtering (WHERE) from group filtering (HAVING).
What to do instead
Underline the requested output columns and the condition in the question before writing the query. Write queries in a fixed order (SELECT columns, FROM table, WHERE condition, GROUP BY, HAVING, ORDER BY) and check each clause against the underlined words. Practise three queries that differ only in WHERE versus HAVING.
Explaining networking concepts with the wrong layer or device, for example placing a router at the data-link layer or describing a hub as intelligent.
Devices, protocols and layers are memorised as separate lists, and students never map device to layer to function, so items get shuffled in recall.
What to do instead
Create a three-column table (device or protocol, OSI layer, one-line function) and fill it for hub, switch, router, IP, TCP, UDP, HTTP and Ethernet. Test yourself by covering one column at a time. Add a note on why a switch uses MAC addresses and a router uses IP addresses.
Giving definitions of software types (system versus application, compiler versus interpreter) without the distinguishing comparison the marking scheme rewards.
Students answer the literal question ('define compiler') and stop, missing that PSEB questions usually carry marks for differences, examples and advantages.
What to do instead
For every 'define' question, add one example and one contrast sentence. Prepare a comparison table for compiler versus interpreter and system versus application software with at least three points of difference, and reproduce it in answers when the mark weight is more than two.
Leaving flowcharts and algorithms incomplete: missing the START/STOP terminators, missing the decision labels Yes/No, or writing an algorithm that has no input step.
Students treat these as decoration rather than syntax, and they draft the flowchart after the code rather than before, so steps are skipped.
What to do instead
Use a checklist for every flowchart: one START, one STOP, arrows on every connector, Yes/No on every diamond, input before processing. Write the algorithm first in numbered steps, then draw the flowchart directly from it, and compare the two for missing steps.
Misreading the mark allocation and writing a long essay for a two-mark question while leaving a six-mark question with two lines.
Candidates answer in the order they feel confident and run out of time on high-weight questions, and they do not know how many points a marking scheme expects per mark.
What to do instead
In the first five minutes, mark each question with its mark value and plan roughly one distinct point per mark. Answer high-weight questions first while fresh, and keep short-answer questions to the point count. Rehearse with a timed paper using this allocation before the exam.