Mumbai University Solved Question Papers
October 2025
Previous Year Question Paper with Solution
BSc IT · Sem VI
October 2025 - Software Testing and Quality Assurance Examination
munotes.in
Mumbai
BSc IT Sem VI October 2025 Software Testing and 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 4 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 Testing and Quality Assurance examination.
Contents
The questions below are the paper as the University of Mumbai set it at the October 2025 - Software Testing and 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 Testing and 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.What are the core components of quality? Briefly explain each with an example.[5]
Answer
For full marks, cover: what quality means, then each core component (customer focus, defined requirements, management leadership, process orientation, people involvement, measurement and continual improvement) with a software example, and how they fit together.
What quality means
Quality is the degree to which a product meets the requirements and needs of its users. Philip Crosby put it as "conformance to requirements"; the user's view adds fitness for use. For software, ISO/IEC 25010:2023 describes product quality through nine characteristics, such as functional suitability, reliability, security and maintainability.
Quality does not happen by chance. It rests on a few core components.
The core components
- Customer focus. Quality is judged finally by the customer's satisfaction. Example: a banking app that is technically correct but confusing to use fails its customers, so usability is part of its quality.
- Defined quality requirements. Quality must be defined in measurable terms before it can be achieved. Example: "the results page must load within 2 seconds for 10,000 users at once" can be tested; "the site must be fast" cannot.
- Management leadership and commitment. Management sets the quality policy, provides resources and leads improvement. Example: a manager who allows time for code reviews even under deadline pressure.
- Process orientation. Quality comes from well-defined, repeatable processes, not from heroic individuals. Example: a defined process for requirement reviews, coding standards and testing before every release.
- People involvement and training. Every person, not only testers, is responsible for quality. Example: developers write unit tests and are trained in secure coding.
- Measurement. What is not measured cannot be managed. Example: tracking defect density per thousand lines of code and defects found after release.
- Continual improvement. Processes are reviewed and improved using data, through the Plan-Do-Check-Act cycle. Example: after finding many defects from unclear requirements, a team adds a requirements checklist.
How they fit together
Draw a cycle:
- Customer needs -> defined requirements.
- Processes run by trained people under committed management -> product.
- Measurement of results -> improvement -> back to meeting customer needs.
Quality views
| View | Quality means |
|---|---|
| Customer | fitness for use, satisfaction |
| Producer | conformance to requirements |
| Product | the nine ISO/IEC 25010 characteristics |
| Value | quality worth its cost |
Conclusion. The core components of quality are customer focus, defined and measurable requirements, management leadership and defined processes. The involvement and training of people, measurement and continual improvement complete them. Together they turn quality from a hope into a managed result that satisfies the customer.
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.