Assam ASSEB HSLC Elective Computer Science common mistakes
Assam ASSEB HSLC Elective Computer Science · Understand the traps and how to avoid them.
When converting between decimal and binary, the candidate divides by 2 but writes the remainders in the order they were produced (top-to-bottom) instead of reading them bottom-to-top, so 13 comes out as 1011 instead of 1101.
The repeated-division method is memorised as a list of steps without the reason: the first remainder is the least significant bit, so the last remainder becomes the leading bit. Candidates also skip the final quotient of 1, which is itself a remainder.
What to do instead
After every conversion, verify by expanding the binary answer back into powers of 2 (8+4+1=13). Practise five conversions each way per session and always write the quotient column and the remainder column separately, then copy remainders upward with an arrow drawn on the page.
The candidate labels 1024 bytes as 1 KB and 1000 bytes as 1 KB interchangeably within the same answer, and mixes decimal (KB, MB) and binary (KiB, MiB) prefixes when computing storage sizes.
Textbooks and pen drives use both conventions, and candidates never decide which one the question expects. They also confuse bit and byte when a question gives speed in Mbps and size in MB.
What to do instead
Adopt the convention used in the Assam board syllabus (1 KB = 1024 bytes) and state it explicitly in the answer. For speed-and-size problems, convert bits to bytes by dividing by 8 first, then divide by 1024 step by step, showing each step.
Asked to distinguish RAM and ROM or primary and secondary memory, the candidate writes two loose paragraphs of description instead of point-by-point contrast, and never mentions volatility, writeability, or typical use.
The candidate answers the topic rather than the instruction word 'distinguish'. Marking schemes award one mark per valid contrasting pair, so prose without paired points scores poorly even when the facts are right.
What to do instead
Answer comparison questions in a two-column table with at least four matched rows (volatility, read/write, speed, cost per bit, example). Before writing, underline the command word in the question and match the answer format to it: define, list, differentiate, or explain.
The candidate describes a file operation by naming only the menu, for example 'use the File menu to save', without giving the actual keystroke sequence or the dialog steps, and omits the extension when naming a saved file.
Practical GUI steps are learned by watching, not by rehearsing them in words; under exam pressure the candidate recalls the general area of the screen but not the exact path, and treats the file name as unimportant.
What to do instead
Rehearse each common operation aloud as a numbered sequence, e.g. File > Save As > choose folder > type name with .docx > Save. On the practical record, always write the full file name with extension and the folder path, and practise the same sequence on the lab machine until it is automatic.
In a word processor question, the candidate claims that pressing Enter creates a new page or that changing the font size changes the page margins, and cannot say what the ruler, tab stops, or section breaks do.
Everyday typing habits are mistaken for document-model knowledge; candidates never separate character formatting, paragraph formatting, and page setup into distinct layers, so they attribute any visible change to the wrong tool.
What to do instead
Build a one-page reference sheet with three headings (character, paragraph, page) and place each feature under the correct heading. Test each claim on a lab machine: press Enter and observe, insert a page break and observe, change margins and observe, then note the difference in one line.
When writing a spreadsheet formula, the candidate types the numbers directly (for example =25+30+45) instead of referring to cells, forgets the leading equals sign, or writes a range as A1-A10 rather than A1:A10.
The candidate is solving the arithmetic rather than the spreadsheet task, and the colon-versus-hyphen range syntax is easy to misremember because both appear on the same keyboard row. Without the equals sign the entry becomes plain text and no error appears, which hides the mistake.
What to do instead
Follow a fixed rule: every formula starts with =, every range uses a colon, and every input is a cell reference. After entering a formula, change one source cell and confirm the result updates; if it does not, the formula was typed as text. Practise SUM, AVERAGE, MAX, MIN, and one IF per lab session.
On a presentation question, the candidate puts whole paragraphs onto a single slide, uses many fonts and colours, and cannot explain the difference between a slide transition and an object animation.
The candidate equates 'more content' with 'more marks' and has never been taught design constraints. Transition and animation are both 'movement' in the candidate's mind, so the distinction between slide-level and object-level effects is lost.
What to do instead
Apply a hard rule of no more than six bullet lines and six words per line on any slide, one font family, and one accent colour. Memorise the distinction with a sentence: a transition moves from one slide to the next, an animation moves an object within a slide. Build a five-slide project deck and get it reviewed against these rules.
The candidate confuses the World Wide Web with the Internet, calls a browser a search engine, and cannot separate an email address into local part, @ symbol, and domain, or name the roles of To, Cc, and Bcc.
In daily use the browser opens a search page immediately, so the browser and the search engine appear to be one thing. Cc and Bcc are rarely used by students, so their purpose is guessed rather than known.
What to do instead
Draw a layered diagram: Internet (the network) at the bottom, web services and email above it, browser as the client program, search engine as a website. Write one email address and label its three parts. State Cc as visible copy and Bcc as hidden copy, and give one situation where Bcc protects privacy.
Asked to write an algorithm or a short program, the candidate starts typing code without stating the steps, omits initialisation of variables, and uses a single equals sign for comparison in a condition.
The candidate treats programming as syntax recall rather than problem decomposition, and the difference between assignment and comparison is invisible when both are written with = in everyday maths.
What to do instead
Always write the algorithm in numbered plain-language steps first, then translate line by line. Use a fixed skeleton: declare and initialise variables, read input, process, print output. Circle every condition and check it uses == or the correct relational operator; dry-run the program on paper with one sample input before writing the final answer.
On cyber safety questions, the candidate defines a strong password as 'one that is hard to guess' without naming length, mixed character types, or reuse, and cannot identify a phishing message because it looks like a normal email.
Safety topics are treated as general awareness rather than examinable content, so answers stay at the level of slogans. Phishing recognition needs concrete cues, and candidates have never been given a checklist of them.
What to do instead
Memorise four password criteria (at least 12 characters, upper and lower case, digits, symbols, never reused) and five phishing cues (unknown sender, urgency, spelling errors, mismatched link, request for credentials or OTP). Apply the checklist to two sample messages and write which cue each one triggers.