MCA_NEW · Semester 1 · Practical labs
Lab viva prep
Everything for the MCSL-216 and MCSL-217 vivas, starting from zero. Your assignment work explained in plain words, every recent term-end practical paper solved step by step, and flashcards until you can answer without looking.
DAA and Web Design Lab
Algorithm programs in C and a validated web form that saves to a database.
6 past papers solved · 129 viva questions
MCSL-217Software Engineering Lab
Design documents for a software system: scope, DFDs, ERDs, data dictionary, estimates and test cases.
7 past papers solved · 102 viva questions
How IGNOU conducts the viva
A viva is an oral exam about your work. There are two different vivas for a lab course. Check your study centre notice or hall ticket to see which one you have. Both guides cover both.
About the assignment you submitted
- Held at your study centre.
- 20 marks of the assignment are for the viva. The rest is your written work.
- Compulsory. If you submit the assignment but miss the viva, the assignment counts as not done and gets zero.
- The examiner asks you to explain your own programs and diagrams, why you chose each step, and the theory behind them.
Prepare with: "Your assignment, explained" in each guide.
A lab exam, then a viva on it
- 2 hours, 50 marks: two compulsory questions of 20 marks each, and 10 marks of viva. Every MCSL-216 and MCSL-217 paper from December 2024 and June 2025 follows this pattern.
- You get a set (I to IV). You write and run the programs on the lab computer (216) or write the design work (217).
- The examiner checks your output, then asks about what you just did.
- You need 75% attendance in the practical counselling sessions to be allowed to sit it.
Prepare with: "Past papers, solved" in each guide. The same questions keep coming back.
What the examiner does
Asks about your work
"Explain your program." "Why greedy?" "Why is Order Item weak?" This is most of the marks, and it is the part you control.
Asks you to run or change it
Search for a number that is not in the array. Add a phone field to the form. Sort the other way. Practise these once tonight.
Asks theory around it
Complexity, GET vs POST, primary key, DFD levels, black-box testing. Short, correct answers beat long, shaky ones.
How to answer
The shape of a good answer
- One plain sentence that answers the question.
- One example from your own assignment.
- Stop, and let them ask the next thing.
When you don't know
- Say "I'm not fully sure, but I think…" and give your reasoning.
- Link it to what you know: "I haven't used that, but in my program I did…"
- Ask to draw it or write it. It gives you time to think.
- Never make up code or a definition with confidence. Examiners notice.
Carry with you
- Hall ticket and IGNOU identity card.
- Your assignment copy and lab record, if your centre asked for them.
- Two pens, a pencil, an eraser and a ruler for diagrams.
If the viva is tomorrow
| Time | Do this |
|---|---|
| 60 min | MCSL-216 assignment. Run the three programs once. Say each 30-second answer out loud twice. Trace binary search for 100 and for 42. |
| 45 min | MCSL-217 assignment. Learn the 9 entities, why Order Item is weak, and why stock quantity sits on the STOCKS relationship. |
| 90 min | Past papers if it is the term-end practical: the form template, merge sort, knapsack and matrix loop counts for 216; DFDs, scope and test cases for 217. |
| 45 min | Drill the ★ cards in both guides until most are green. |
| Morning | Only the 30-second answers and the summary at the top of each guide. |
Where this comes from
The exam pattern and every past question come from IGNOU's own question papers. The viva rules come from IGNOU's assignment booklets and programme guide. Always check your own study centre's notice for dates and mode.