MCA-239 Software Quality Management Notes cover all 4 units of this GGSIPU MCA Semester 3 elective in 59 pages, with 32 solved short answers, 37 long-answer practice questions, 5 solved numericals and 23 numbered diagrams. They follow the official MCA syllabus for affiliated institutes, applicable from academic session 2025-26 onwards.
Written by Prateek Talwar, Founder, Unnati Educations · Reviewed by Ritik Rawat, B.Tech, Senior Full Stack Developer · Checked against the official MCA scheme and syllabus PDF (approved 1 Aug 2025) · Updated 14 October 2026 · Editorial policy
Scheme: MCA (2 years), affiliated institutes, A.S. 2025-26 onwards | Applies to: batches admitted from 2025-26 | Verified against: syllmcaaff050825900p.pdf, 1 Aug 2025
MCA-239 Software Quality Management at a glance: GGSIPU MCA Sem 3 credits, units and exam pattern
MCA-239 is one of eleven Core Elective - III options; its prerequisite is "Fundamentals of Software Engineering".
| Code and title | MCA-239 Software Quality Management |
|---|---|
| Course and semester | MCA (2 years), Semester 3 |
| Category and credits | Core Elective - III · 3 credits · L 3, T/P 0 |
| Marks | 100: 40 internal + 60 end-term |
| End-term pattern | Q1 compulsory, short or objective questions on the whole syllabus, 12 marks; then 1 of 2 questions from each unit, 12 marks each (12 + 48 = 60 marks) |
| Pass mark | 40 out of 100 |
| Units | 4, with 10 lecture hours each |
| Applies to | Academic session 2025-26 onwards |
| Paired lab | MCA-267 Software Quality Management Lab · 0-2 · 1 credit |
The programme runs under GGSIPU Ordinance 11, as point 8 of the scheme notes. Its semester siblings are listed under GGSIPU MCA Semester 3 papers.
MCA-239 Software Quality Management Notes unit-wise: 32 solved short answers and 5 solved numericals across 4 units
Each unit ends with 8 solved short answers, long-answer practice questions and a revision table. These MCA-239 Software Quality Management IPU notes favour tables and diagrams over long paragraphs. Other papers of the course sit under GGSIPU MCA notes.
MCA-239 Unit 1: Fundamentals of Software Quality and Software Quality Assurance
Unit 1 (pages 5 to 19, 11 sections, 6 figures) covers five quality definitions from IEEE 610.12 to Juran, the error, fault and failure chain, Galin's nine causes of errors, the six classes of SQA components, McCall's 11 factors with an example requirement each, the alternative models, ISO/IEC 25010 and SQA tools. It has 8 short and 9 long questions.
| Basis | SQA | SQC |
|---|---|---|
| Focus | Process | Product |
| Approach | Preventive | Detective, corrective |
| Timing | Whole life cycle | After a work product is built |
| Objective | Cut the cost of guaranteeing quality | Withhold non-conforming products |
Quick look: SQA versus SQC (from page 11)
- Basis
- Focus
- SQA
- Process
- SQC
- Product
- Basis
- Approach
- SQA
- Preventive
- SQC
- Detective, corrective
- Basis
- Timing
- SQA
- Whole life cycle
- SQC
- After a work product is built
- Basis
- Objective
- SQA
- Cut the cost of guaranteeing quality
- SQC
- Withhold non-conforming products
MCA-239 Unit 2: Tailoring the SQA System and Participants in Software Quality Management
Unit 2 (pages 20 to 34, 11 sections, 7 figures) covers the SQA architecture, two-stage contract review, development and quality plans, formal design reviews, audits, testing with stubs and drivers, and maintenance quality, closing on the roles of management, the SQA unit, trustees and committees. It has 8 short and 10 long questions.
| Audit type | Who audits | Purpose |
|---|---|---|
| Internal (first-party) | Own SQA unit | Check projects follow procedures |
| External (second-party) | Customer audits supplier | Confirm the quality plan is followed |
| Certification (third-party) | Independent body | Award or renew ISO 9001 or CMMI |
| Process audit | SQA unit | Is the process run as defined? |
Quick look: who carries out each audit (from page 26)
- Audit type
- Internal (first-party)
- Who audits
- Own SQA unit
- Purpose
- Check projects follow procedures
- Audit type
- External (second-party)
- Who audits
- Customer audits supplier
- Purpose
- Confirm the quality plan is followed
- Audit type
- Certification (third-party)
- Who audits
- Independent body
- Purpose
- Award or renew ISO 9001 or CMMI
- Audit type
- Process audit
- Who audits
- SQA unit
- Purpose
- Is the process run as defined?
MCA-239 Unit 3: CASE Tools in Software Quality and Software Quality Metrics
Unit 3 (pages 35 to 46, 13 sections, 3 figures) has two parts. Part A covers upper, lower and integrated CASE, the shared repository and what CASE adds to product, maintenance and project quality. Part B gives IEEE 1061 metrics, function points, every Galin process and product formula, McCabe and Halstead. It has 3 solved numericals, 8 short and 9 long questions and a formula sheet.
| Metric | Working | Result |
|---|---|---|
| CED | 180 / 40 | 4.5 errors per KLOC |
| WCED | 460 / 40 | 11.5 per KLOC |
| ASCE | 460 / 180 | 2.56 |
| DevP | 8000 / 40 | 200 hours per KLOC |
Quick look: metrics for a 40 KLOC project with 180 code errors (from page 41)
- Metric
- CED
- Working
- 180 / 40
- Result
- 4.5 errors per KLOC
- Metric
- WCED
- Working
- 460 / 40
- Result
- 11.5 per KLOC
- Metric
- ASCE
- Working
- 460 / 180
- Result
- 2.56
- Metric
- DevP
- Working
- 8000 / 40
- Result
- 200 hours per KLOC
MCA-239 Unit 4: SQA Standards, Costs of Software Quality and Future of Software Quality
Unit 4 (pages 47 to 59, 7 sections, 7 figures) covers "what" versus "how" standards, Six Sigma, ISO 9001 clauses mapped to PDCA, CMM and CMMI levels, ten IEEE standards with examples, the classic and extended cost of quality models, and SQA challenges and capabilities. It has 2 solved numericals, 8 short and 9 long questions.
| Step | Working | Result |
|---|---|---|
| Opportunities | 500 × 10 | 5,000 |
| DPO | 25 ÷ 5,000 | 0.005 |
| DPMO | 0.005 × 10,00,000 | 5,000 |
| Sigma level | Between 4σ and 4.5σ | About 4.1σ |
Quick look: DPMO for 500 modules with 25 defects (from page 49)
- Step
- Opportunities
- Working
- 500 × 10
- Result
- 5,000
- Step
- DPO
- Working
- 25 ÷ 5,000
- Result
- 0.005
- Step
- DPMO
- Working
- 0.005 × 10,00,000
- Result
- 5,000
- Step
- Sigma level
- Working
- Between 4σ and 4.5σ
- Result
- About 4.1σ
MCA-239 exam corner: 32 solved short answers and 37 long-answer practice questions by unit
Short answers carry model answers and suit Q1; long-answer questions are for practice.
| Unit | Solved short | Long practice | Numericals |
|---|---|---|---|
| Unit 1 | 8 | 9 | 0 |
| Unit 2 | 8 | 10 | 0 |
| Unit 3 | 8 | 9 | 3 |
| Unit 4 | 8 | 9 | 2 |
| Total | 32 | 37 | 5 |
MCA-239 exam material per unit
- Unit
- Unit 1
- Solved short
- 8
- Long practice
- 9
- Numericals
- 0
- Unit
- Unit 2
- Solved short
- 8
- Long practice
- 10
- Numericals
- 0
- Unit
- Unit 3
- Solved short
- 8
- Long practice
- 9
- Numericals
- 3
- Unit
- Unit 4
- Solved short
- 8
- Long practice
- 9
- Numericals
- 2
- Unit
- Total
- Solved short
- 32
- Long practice
- 37
- Numericals
- 5
The MCA-239 notes solve 32 short-answer questions across 4 units, list 37 long-answer practice questions and work 5 numericals step by step.
One question per unit, with answer pointers:
- Unit 1: Differentiate error, fault and failure. Pointer (page 17): one line each, then "not every error is a fault, not every fault is a failure".
- Unit 2: What are stubs and drivers? Pointer (page 33): a stub replaces a called module in top-down testing; a driver calls the module under test in bottom-up testing.
- Unit 3: Cyclomatic complexity of a graph with 13 edges and 10 nodes? Pointer (page 45): V(G) = 13 − 10 + 2 = 5 independent paths.
- Unit 4: What does the extended cost model add? Pointer (page 58): managerial preparation and control costs, and managerial failure costs such as late-delivery damages.
More practice sits in the MCA-239 important questions.
Who writes and checks the MCA-239 SQM notes?
- Prateek Talwar, author: Founder, Unnati Educations; Associate Company Secretary (ACS), ICSI, membership no. 58704, since 15 May 2019; B.Com, University of Delhi (School of Open Learning), 2012. Profile
- Ritik Rawat, subject reviewer: B.Tech; Senior Full Stack Developer, Unnati Educations.
The review checked metric notation (NCE, KLMC, NYF), function point weights and CMM versus CMMI level names. These GGSIPU MCA Sem 3 Software Quality Management notes were mapped to the 2025-26 syllabus and updated on 14 October 2026; the 2026-27 edition adds CMMI V3.0.
How we write and check notes is set out in our editorial policy.
The same team prepares GGSIPU important questions for every course.
How to write MCA-239 answers: definition tables, Galin diagrams and formula-based metric numericals
Short answers
Standard definition (IEEE, Galin or ISO), then one example; for "differentiate", a small table. Page 12 says to end SQA versus SQC with "SQC is a subset of SQA".
Long answers
Open with a labelled diagram, then three or four lines per block: the six-class figure for SQA components (page 13), the organisational base for participants (page 32), stressing SQA unit independence. For CASE tools, use the syllabus headings: product, maintenance, project.
Numericals
Page 44 sets the rule: formula, substitution, result with unit, and percentages for DERE, TTO and availability.
Worked example: function points (page 40)
- CFP from five component types = 89; sum of 14 complexity grades RCAF = 38.
FP = 89 × (0.65 + 0.01 × 38) = 89 × 1.03 = 91.67 ≈ 92 FP- Show the CFP table by component first; most marks sit there.
Watch the level names: level 2 is "Repeatable" in CMM, "Managed" in CMMI. Practise on GGSIPU MCA important questions.
MCA-239 and the GGSIPU MCA Sem 3 papers it connects to
Every Semester 3 paper and lab, with its course outcomes, is on the GGSIPU MCA syllabus page.
Paired lab: MCA-267 Software Quality Management Lab, where you build SQA plans with IBM RUP or StarUML:
- Unit 2 quality plan elements feed building an SQA plan (CO1, CO6).
- Unit 3 upper CASE tools such as StarUML feed modelling for CO1.
- Unit 2 checklists and templates feed checklist reviews (CO3).
MCA-104 Object Oriented Software Engineering gives the background Unit 1 assumes.
Core Sem 3 papers: MCA-201 Design and Analysis of Algorithms, MCA-203 Artificial Intelligence and Machine Learning.
Core Elective - II: MCA-205 Statistics and Data Analytics, MCA-207 Enterprise Computing with JAVA, MCA-209 Natural Language Processing, MCA-211 Computer Graphics, MCA-213 Wireless Sensor Networks, MCA-215 Software Project Management, MCA-217 Advanced Computer Architecture, MCA-219 Distributed Systems, MCA-221 Applied Cryptography, MCA-223 Cloud Computing, MCA-225 e-Business Systems.
Core Elective - III alternatives: MCA-227 Web Intelligence and Big Data, MCA-229 Flutter and Dart, MCA-231 Service Oriented Architecture, MCA-233 Multimedia Technologies, MCA-235 Internet of Things, MCA-237 Soft Computing, MCA-241 Digital Image Processing, MCA-243 Compiler Design, MCA-245 Parallel Computing, MCA-247 Numerical and Scientific Computing.
Open Elective - II: MCA-249 Research Methodology, MCA-251 Operational Research, MCA-253 Cyber Security and Cyber Laws, MCA-255 e-Content Development. Also MCA-261, MCA-263 and MCA-265 labs, MCA-269 Minor Project - III, MCA-271 Entrepreneurship Mindset and MCA-273 Professional Proficiency - III.
Inspection and walkthrough in SQA reviews: excerpt from page 25 of the MCA-239 notes
Excerpt from page 25
Who sits on a formal design review
The review leader should know the project type, be at least as senior as the project leader, get on well with the team and, above all, not belong to the project team, so the review stays independent. Often this is a senior manager or the head of the SQA unit. The team draws on senior project members, professionals from other projects, customer-user representatives and sometimes outside consultants. Three to five members is ideal.
Three stages and three decisions
In preparation, the leader appoints the team, members read the document and list comments, and the developers prepare a short presentation. The session covers that presentation, comments, verification and validation, and a decision. Afterwards a DR report is circulated and the leader follows up corrections.
The decision is full approval (move on, perhaps with minor fixes), partial approval (continue some parts, rework others) or denial of approval (repeat the review after major corrections).
Peer reviews detect, they do not approve
Peer reviews are done by colleagues at the author's own level. They cannot approve a document; their job is to find as many errors as possible. The two methods are inspection, the formal one introduced by Michael Fagan at IBM in 1976, and walkthrough, the less formal one.
Inspection
An inspection has a trained moderator who leads and follows up, the author who answers questions, and specialists such as a designer, a coder and a tester. It moves through planning, an overview by the author, preparation with checklists, the session (a reader paraphrases while defects are logged), rework and follow-up.
Walkthrough
A walkthrough has a coordinator, the author, a standards enforcer, a maintenance expert and a user representative. There is no overview meeting, preparation is brief, the author walks the team through the document and follow-up is informal. Inspections collect defect data and detect more errors; walkthroughs detect fewer but double as training.
Do the MCA-239 notes cover the full GGSIPU syllabus?
Yes. Every topic under the four units of the 2025-26 MCA-239 syllabus has a matching section in the notes; no gaps were found. The PDF gives topic headings, not unit titles, so the unit names here join those headings.
| Unit | Official topics | In the notes | Status |
|---|---|---|---|
| I | Software quality, SQA context, challenges, environments, SDLC, SQA versus SQC | Sections 1-6, pp. 6-12 | Covered |
| I | SQA system components, quality factors (operation, revision, transition), alternative models, SQA tools | Sections 7-11, pp. 12-17 | Covered |
| II | SQA architecture, contract review, quality plans, review, audit, testing | Sections 1-8, pp. 21-29 | Covered |
| II | Infrastructure and management components, organising SQA, construction guidelines, SQA management roles | Sections 9-11, pp. 29-32 | Covered |
| III | CASE tools and their contribution to product, maintenance and project quality | Part A, pp. 36-38 | Covered |
| III | Metrics classification, process and product metrics, implementation, limitations | Part B, pp. 38-44 | Covered |
| IV | Scope of standards, Six Sigma, ISO, CMMI, IEEE with examples | Sections 1-5, pp. 48-53 | Covered |
| IV | Cost of quality metrics, classic and extended models, application, problems, SQA challenges and capabilities | Sections 6-7, pp. 54-57 | Covered |
MCA-239 official topics mapped to the notes
- Unit
- I
- Official topics
- Software quality, SQA context, challenges, environments, SDLC, SQA versus SQC
- In the notes
- Sections 1-6, pp. 6-12
- Status
- Covered
- Unit
- I
- Official topics
- SQA system components, quality factors (operation, revision, transition), alternative models, SQA tools
- In the notes
- Sections 7-11, pp. 12-17
- Status
- Covered
- Unit
- II
- Official topics
- SQA architecture, contract review, quality plans, review, audit, testing
- In the notes
- Sections 1-8, pp. 21-29
- Status
- Covered
- Unit
- II
- Official topics
- Infrastructure and management components, organising SQA, construction guidelines, SQA management roles
- In the notes
- Sections 9-11, pp. 29-32
- Status
- Covered
- Unit
- III
- Official topics
- CASE tools and their contribution to product, maintenance and project quality
- In the notes
- Part A, pp. 36-38
- Status
- Covered
- Unit
- III
- Official topics
- Metrics classification, process and product metrics, implementation, limitations
- In the notes
- Part B, pp. 38-44
- Status
- Covered
- Unit
- IV
- Official topics
- Scope of standards, Six Sigma, ISO, CMMI, IEEE with examples
- In the notes
- Sections 1-5, pp. 48-53
- Status
- Covered
- Unit
- IV
- Official topics
- Cost of quality metrics, classic and extended models, application, problems, SQA challenges and capabilities
- In the notes
- Sections 6-7, pp. 54-57
- Status
- Covered
Verify it yourself in the official MCA scheme and syllabus, affiliated institutes, A.S. 2025-26 onwards (MCA-239 is on PDF pages 149-150).
Every course in GGSIPU notes is mapped to its official PDF the same way.
MCA-239 SQM notes FAQs
How do I get the full MCA-239 notes?
Message us on WhatsApp at 9899436384 with the code MCA-239. The full notes come as a printed book only; they are not sold as a PDF. Once the order is confirmed on WhatsApp, the book is dispatched to your address and reaches you within 5 to 7 days at most, depending on your location. Check the layout first with the "View Sample PDF" button.
What is the passing mark for MCA-239 Software Quality Management?
MCA-239 is marked out of 100: 40 internal and 60 end-term. The MCA scheme of examination states pass marks as 40 out of 100 for every paper, which is 40%. For end-term minimums, re-appear rules and anything else not printed in the scheme, check GGSIPU Ordinance 11 on ipu.ac.in, which the MCA scheme says governs the programme.
Why do the MCA-239 notes label answers 2.5 and 12.5 marks?
The notes tag short answers "2.5 Marks" and long answers "12.5 Marks". The 2025-26 MCA-239 pattern is different: Q1 carries 12 marks in total and each unit question carries 12 marks. Use the short answers as parts of Q1 and the long answers as full unit questions, and plan each long answer for 12 marks.
Which MCA-239 unit has numericals?
Units 3 and 4. Unit 3 has three solved numericals (function points, a seven-metric process set, and availability with help-desk and failure density) plus a worked cyclomatic complexity example. Unit 4 has two: DPMO with sigma level, and classifying costs under the extended cost model. Page 45 lists every Unit 3 formula on one page.
Is MCA-239 compulsory in GGSIPU MCA Semester 3?
No. MCA-239 is one of eleven options in the Core Elective - III slot, and you choose one. The scheme also says an elective needs at least 20 students for classes to run; with fewer, students may have to complete it on SWAYAM or a similar MOOC with prior approval, while still sitting the institute's evaluation.
Do the MCA-239 notes cover the MCA-267 Software Quality Management Lab?
No. This book covers the MCA-239 theory paper only and has no practical records. The lab asks you to build and check SQA plans with tools such as IBM RUP or StarUML. Units 2 and 3 explain quality plans, checklists and CASE tools, which is the theory behind those practicals, so the book helps you prepare for them.
Get the full MCA-239 Software Quality Management Notes on WhatsApp
These Software Quality Management notes in English are sold as a printed book only, not as a PDF. Delivery: within 5 to 7 days at most; the exact time may vary with your location.
Order the full MCA-239 Software Quality Management Notes book on WhatsApp (4 units, 59 pages)
Unnati Educations is an independent education provider based in Vikaspuri, Delhi. We are not affiliated with, authorised by, or endorsed by Guru Gobind Singh Indraprastha University (GGSIPU). 'GGSIPU' and 'IPU' are used only to describe the syllabus our notes follow. For official information, visit ipu.ac.in.
Ready for the full notes?
Discuss coverage and delivery with our team.