Mumbai University Solved Question Papers
October 2025
Previous Year Question Paper with Solution
BSc IT · Sem VI
October 2025 - Software Quality Assurance Examination
munotes.in
Mumbai
BSc IT Sem VI October 2025 Software Quality Assurance Question Paper with Solutions
Get access to whole semester resourcesSemester Pass
MU B.Sc. (Information Technology) student group
Free to join
First published on munotes.in on 5 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 October 2025 - Software Quality Assurance examination.
Contents
The questions below are the paper as the University of Mumbai set it at the October 2025 - Software Quality Assurance examination, in the order it was set.
MarksPage
MarksPage
MarksPage
The Paper as Set
The questions in this volume are the questions asked at the October 2025 - Software Quality Assurance 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 · 30 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.
SECTION I
1.
Attempt any three of the following · 15 Marks
a.Explain any five principles of Total Quality Management with suitable examples.[5]
Answer
For full marks, cover: what TQM is in one paragraph, five principles each with its meaning and a software example, how they work together, and the result for the organisation.
TQM in brief
Total Quality Management (TQM) is a way of running an organisation in which everyone, led by top management, works continually to satisfy customers. Quality is built into every process instead of being inspected at the end. It draws on the ideas of Deming, Juran, Crosby, Feigenbaum and Ishikawa.
Five principles
1. Customer focus. The customer decides what quality is. Every process is judged by what it adds for the customer, inside or outside the company. Example: a bank's app team watches how customers use the app and finds that most give up on a long sign-up form. Shortening it raises completed sign-ups, even though no "defect" was ever reported.
2. Total employee involvement. Quality is everyone's job, not only the testers'. People are trained, trusted and encouraged to suggest improvements. Example: developers write unit tests and review each other's code; support staff pass customer complaints straight to the product team.
3. Process-centred approach. Work is seen as processes with inputs, steps and outputs. Defined, measured processes give repeatable results. Example: a defined release process: code review, automated tests, a staging check and a sign-off, followed for every release.
4. Continual improvement. The organisation keeps finding and fixing weaknesses through the Plan-Do-Check-Act cycle, in small steps and big ones. Example: each quarter the team picks the most common defect cause, changes the process behind it, and checks the defect count the next quarter.
5. Fact-based decision making. Decisions rest on data, not opinion. Example: instead of guessing, the team counts defects by module. Two of twelve modules produce most of them, so testing and redesign go there first.
Other principles often listed are an integrated system, a strategic approach and good communication.
How they work together
| Principle | Supplies |
|---|---|
| Customer focus | The goal |
| Employee involvement | The people |
| Process approach | The method |
| Continual improvement | The direction |
| Fact-based decisions | The evidence |
Draw: a circle labelled "Customer satisfaction" in the centre, with five arrows pointing to it from the five principles.
The result
Fewer defects and less rework, more predictable delivery, more satisfied customers and a team that improves its own way of working.
Conclusion. TQM is an organisation-wide way of satisfying customers through continual improvement. Five of its principles are customer focus, total employee involvement, a process-centred approach, continual improvement and fact-based decision making. In a software team they show up as usability work, shared ownership of testing and defined releases. They also show up as quarterly process fixes and data on where defects arise.
The rest of the answers
The first answer is free. The rest come with the B.Sc. (Information Technology) Semester 6 solved papers.
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.
Found an error in this volume? Report it and we will check it against the paper.