Mumbai University Solved Question Papers munotes.in
Software Engineering
BSc CS · Sem 4
Mar 2025 Examination
Previous Year Question Paper with Solution
munotes.in Mumbai
Mumbai University Solved Question Papers munotes.in
Software Engineering
BSc CS · Sem 4
Mar 2025 Examination
Previous Year Question Paper with Solution
munotes.in Mumbai
First published on munotes.in on 12 November 2026.
This edition revised 13 November 2026.
Published by munotes.in, Mumbai.
Model answers written and edited by the munotes.in editorial desk.
Passages from this volume may be quoted, in print, online or by an AI system, with credit: name munotes.in and link to this volume's page. The volume may not be reproduced as a whole. Full terms at munotes.in/content-license.
munotes.in is an independent study resource for students of the University of Mumbai. It is not affiliated with the University of Mumbai, and is not endorsed by it.
The University does not publish an official answer key for this paper. The answers in this volume are model answers, written to show how a full-mark answer is built. They are a study aid, not an authority on what an examiner marked.
The question paper reproduced here is the paper as set by the University of Mumbai at the Mar 2025 examination.
The questions below are the paper as the University of Mumbai set it at the Mar 2025 examination, in the order it was set.
MarksPage
MarksPage
The questions in this volume are the questions asked at the Mar 2025 examination, reproduced as the University of Mumbai set them, in the order it set them. Nothing has been reworded, added or left out. Only the answers are ours. See the original question paper.
Duration 2½ hours · Total marks 75 · 24 questions answered
How to use this volume
Solve the paper first, under exam conditions and against the clock. Then read the answers here and mark your own. Reading a solution before attempting the question feels productive and teaches very little, because recognising an answer is not the same as being able to write one.
Q1)
Answer any four of the following: · 20 Marks
Answer
For full marks, cover: what XP is and where it came from; its five values; its process, drawn; the key practices in their four groups; one example; where it fits and its limits.
Extreme Programming (XP) is an agile method created by Kent Beck. It grew out of the C3 payroll project from 1996. Beck described it in his book Extreme Programming Explained in 1999. Its idea is to take good practices to the extreme. If reviewing code is good, review it all the time, by working in pairs. If testing is good, test all the time, writing each test before the code.
Diagram: a loop of four boxes. Planning (user stories, iteration plan) leads to Design (simple design, CRC cards, spike solutions). Design leads to Coding (pairs, tests first). Coding leads to Testing (unit and acceptance tests). Testing ends in a small release, and the measured velocity feeds the next planning.
Each iteration lasts one to three weeks and ends in a small working release.
| Group | Practice | What it means |
|---|---|---|
| Feedback | Pair programming | two people at one computer: a driver types and a navigator reviews; roles swap often |
| Feedback | Planning game | release and iteration planning from user stories; velocity decides how much fits |
| Group | Practice | What it means |
|---|---|---|
| Feedback | Test-driven development | write a failing test, write just enough code, run all tests, then refactor |
| Feedback | Whole team | a real user is on hand at all times to answer questions |
| Process | Continuous integration | code is merged every few hours, with an automated build and tests |
| Process | Refactoring | the structure is improved without changing behaviour; the tests prove it |
| Process | Small releases | working software reaches the customer often |
| Understanding | Coding standards, collective ownership | one style for all code, and anyone may improve any part |
| Group | Practice | What it means |
|---|---|---|
| Understanding | Simple design, system metaphor | the simplest design that passes the tests, and one shared picture of the system |
| Welfare | Sustainable pace | at most 40 hours a week, and no overtime two weeks running |
The practices support one another. Refactoring is safe only because the tests run all the time.
In a college canteen ordering app (our own example), the canteen manager joins the team as its customer. She writes the story "a student orders lunch before 11 a.m.". A pair first writes a test that an order at 11.05 a.m. is refused. Then they write just enough code to pass it.
XP suits small teams, requirements that keep changing, and a customer who can stay with the team. Its limits are a single on-site customer, little design done up front and the cost of pairs.
Conclusion. XP is an agile method of short iterations driven by five values. Its key practices are pairing, tests first, continuous integration, refactoring and small releases at a sustainable pace.
The rest of the answers
You have read the question paper and its first answer in full. Buy the solved papers once and you can read every answer of every solved paper in this semester.
Notes + practical solutions + solved papers: ₹798 Already bought it? Sign in
Or solved papers only: ₹499
Or notes + practical solutions: ₹499
The question paper itself stays free, and so does the syllabus.
What should we fix or add?
Found an error in this volume? Report it and we will check it against the paper.