How to write a 7-mark answer
A 7-mark question in a Semester 3 paper is marked against a scheme: definition, diagram, explanation, example, and sometimes a comparison or algorithm. Long answers that miss those parts lose marks, and short answers that hit every part often get full marks. This guide shows the structure that works for theory questions in COA, DBMS, DSA and Java, and a separate one for numericals.
How much to write
In a 60-mark, 2-hour mid-sem you have about 2 minutes per mark, so roughly 12 minutes for a 7-mark answer, after leaving time to read and check. That is about one to one and a half pages of normal handwriting, including a diagram. In a 100-mark, 3-hour end-sem the budget is about 1.8 minutes per mark. If you are still writing after 15 minutes, finish the current point and move on.
The structure for theory questions
1. Definition (1 mark). One or two precise sentences, using the textbook terms. "Pipelining is a technique of decomposing a sequential process into sub-operations, each executed in a dedicated segment that operates concurrently with all other segments."
2. Diagram (1–2 marks). Draw it whenever the topic has one: block diagrams, flowcharts, tables, trees, memory layouts. Use a pencil and a scale, label every box and arrow, and give it a caption. A clear diagram often earns marks even when the text is thin, and examiners look for it first.
3. Explanation in points (2–3 marks). Numbered or bulleted points, one idea each, with the key word in bold or underlined. Explain the working step by step, in the order it happens (for example fetch → decode → execute → interrupt check).
4. Example (1 mark). A small worked example, an RTL statement, a short code snippet or a real-world case. "For 4 instructions in a 4-segment pipeline: 4 + 4 − 1 = 7 cycles instead of 16."
5. Advantages, disadvantages or comparison (1 mark), if relevant. Two or three points each, or a small table when the question says "compare" or "differentiate".
6. One-line conclusion (optional). Ties the answer back to the question.
"Differentiate" and "compare" questions
Always use a table with at least five or six rows, each row one basis of comparison (definition, speed, cost, flexibility, example…). Put the basis in the first column. A table is faster to write, easier to mark, and shows you know the parameters of comparison. Add one short example under the table if the question asks for it.
Questions with code (Java, DSA)
- Write a complete, compilable program: imports, class,
main, and the method asked for. Missing semicolons and braces cost marks. - Use meaningful names and a short comment on each logical block.
- Show the output in a box after the program, for the sample input you choose.
- For algorithms, give the algorithm or pseudocode first, then a trace on a small input (a table of the stack, queue or array after each step), then the time complexity.
Numerical questions (CONMP, COA arithmetic, DBMS closures)
- Write the formula first, with every symbol identified ("Simpson's 1/3 rule, n = 6 even, h = 0.2"). The formula alone often carries a mark.
- Show the working in a table (iterations, ordinates, differences, k-values), with the same number of decimal places in every row.
- Box the final answer, with units, and state the accuracy reached ("correct to 3 decimal places since x₄ and x₅ agree").
- If the paper has a misprint or a missing value, state your assumption in one line and carry on; that is what the instructions ask for.
Common ways to lose marks
- Writing a 5-mark answer for a 7-mark question (no diagram, no example).
- A diagram with no labels or no caption.
- Long paragraphs that hide the key words.
- Answering a different question that "looks similar". Re-read the question and answer exactly the parts asked: "explain with diagram and RTL statements" needs both.
- Not numbering the answer the same way as the paper (Q3(b), not "3.2").
Practise it
Pick any 7-mark question from the solved papers, set a 12-minute timer and write your answer. Then compare it with the CampusLoop solution, part by part: definition, diagram, points, example. Two or three of these per subject before the exam make the structure automatic. For the full revision schedule, see the last 7 days plan.