MCA-215 Software Project Management Notes cover all 4 units of the GGSIPU MCA Semester 3 elective in 55 pages, with 9 solved numericals (CPM, PERT, COCOMO I and II, EVM, risk exposure, EMV, make-or-buy and metrics), 80 expected exam questions and 4 quick-revision sheets, mapped to the MCA syllabus for affiliated institutes from 2025-26 onwards.
Written by Prateek Talwar, Founder, Unnati Educations · Reviewed by Ritik Rawat, B.Tech, Senior Full Stack Developer · Checked against the MCA Scheme of Examination and Detailed Syllabus (BoS of USIC&T, 28 July 2025) · Updated 14 October 2026 · Editorial policy
Scheme: MCA scheme 2025-26 (affiliated institutes) | Applies to: academic session 2025-26 onwards | Verified against: MCA Scheme of Examination and Detailed Syllabus, 28 July 2025
MCA-215 Software Project Management at a glance: GGSIPU MCA Sem 3 credits, units and exam pattern
| Code and title | MCA-215 Software Project Management |
|---|---|
| Course and semester | MCA (2 years), Semester 3 |
| Category and credits | Core Elective-II (one of 11); 3 credits; L 3, T/P nil |
| Marks | 60-mark end-term paper; the scheme sets pass marks at 40 out of 100 for every paper; no separate internal split is printed |
| End-term pattern | Q1 compulsory, objective or short-answer, whole syllabus, 12 marks; then attempt one of two questions from each unit, 12 marks each (12 + 48 = 60 marks) |
| Units | 4 units, 10 hours each; no unit titles printed |
| Paired lab | MCA-265 Lab based on Core Elective-II (Software Project Management Lab), 0-2, 1 credit |
Verify these facts in the official GGSIPU MCA syllabus PDF: Semester 3 scheme on page 6, pass-mark note on page 8, MCA-215 syllabus on pages 114 to 116.
Its course outcomes run from scheduling within budget (CO1) to a project that cuts rework (CO6). The list of GGSIPU MCA Semester 3 papers shows it next to MCA-201 and MCA-203.
MCA-215 Software Project Management Notes unit-wise: 9 solved numericals and 80 expected exam questions across 4 units
Units follow the official topic order; titles are the notes' own, as the official PDF gives none. The notes are in Hinglish, with formulas and tables in English. Notes for every other MCA paper sit under GGSIPU MCA notes. Pages 11, 21, 33 and 48 are in the sample PDF.
MCA-215 Unit 1: Introduction to SPM and Project Planning
Unit 1 (pages 4 to 15) covers why software projects are hard (Brooks' four problems), the 10 PMBOK knowledge areas, the life cycle vs the SDLC and the manager's role, then SMART objectives, an 11-part proposal, ROI and NPV budgeting, team structures and usability. It has 12 sections, with nine MS Project / ProjectLibre planning steps, 1 quick example and 20 expected questions.
| Point | Patent | Copyright |
|---|---|---|
| Protects | Invention or process | Expression: code, documents |
| Registration | Compulsory | Automatic |
| Duration | 20 years | Life + 60 years |
| Law | Patents Act 1970, Sec 3(k) | Copyright Act 1957 |
Quick look: patent vs copyright for software in India (from page 12)
- Point
- Protects
- Patent
- Invention or process
- Copyright
- Expression: code, documents
- Point
- Registration
- Patent
- Compulsory
- Copyright
- Automatic
- Point
- Duration
- Patent
- 20 years
- Copyright
- Life + 60 years
- Point
- Law
- Patent
- Patents Act 1970, Sec 3(k)
- Copyright
- Copyright Act 1957
MCA-215 Unit 2: Project Scheduling and Project Cost Management
Unit 2 (pages 16 to 29) is the numerical unit: dependencies, AON vs AOA diagrams, CPM passes, PERT, Gantt charts, crashing and fast tracking, then cost metrics, three estimate types, Delphi, analogy, COCOMO I and II, and earned value. It has 12 sections, 5 solved numericals, 1 quick example and 20 expected questions.
| Mode | a | b | c | d |
|---|---|---|---|---|
| Organic | 2.4 | 1.05 | 2.5 | 0.38 |
| Semi-detached | 3.0 | 1.12 | 2.5 | 0.35 |
| Embedded | 3.6 | 1.20 | 2.5 | 0.32 |
Quick look: Basic COCOMO, E = a(KLOC)b, D = c(E)d (from page 24)
- Mode
- Organic
- a
- 2.4
- b
- 1.05
- c
- 2.5
- d
- 0.38
- Mode
- Semi-detached
- a
- 3.0
- b
- 1.12
- c
- 2.5
- d
- 0.35
- Mode
- Embedded
- a
- 3.6
- b
- 1.20
- c
- 2.5
- d
- 0.32
MCA-215 Unit 3: Project Quality Management and Project HR Management
Unit 3 (pages 30 to 42) has two parts. Part A: cost of quality (the 1:10:100 rule), the four stages of quality management, ISO 9001, CMMI levels, Six Sigma and Ishikawa's seven tools. Part B: HR processes, three CRM types, RACI, motivation theories, staff acquisition and performance reports. It has 13 sections, 1 quick example (DPMO) and 20 expected questions.
Quick look: Tuckman's stages and the manager's role (from page 39)
- Forming: roles unclear; the manager directs.
- Storming: ideas clash; the manager coaches.
- Norming: trust forms; the manager supports.
- Performing: self-organising team; the manager delegates.
- Adjourning: recognition, lessons learnt, release.
MCA-215 Unit 4: Risk, Procurement, Monitoring and Project Closure
Unit 4 (pages 43 to 55) covers Boehm's top 10 risks, the risk register, P-I matrix, EMV and risk responses, then make-or-buy, contracts, procurement phases, progress charts, SCM, metrics and closure. It has 13 sections, 4 solved numericals and 20 expected questions.
| Risk | P | Loss | RE (rank) |
|---|---|---|---|
| Key developer leaves | 0.3 | ₹4,00,000 | ₹1,20,000 (2) |
| Requirements change | 0.6 | ₹2,50,000 | ₹1,50,000 (1) |
| Server failure | 0.1 | ₹5,00,000 | ₹50,000 (4) |
| Vendor delay | 0.4 | ₹1,50,000 | ₹60,000 (3) |
Quick look: risk exposure ranking, RE = P × L (from page 47)
- Risk
- Key developer leaves
- P
- 0.3
- Loss
- ₹4,00,000
- RE (rank)
- ₹1,20,000 (2)
- Risk
- Requirements change
- P
- 0.6
- Loss
- ₹2,50,000
- RE (rank)
- ₹1,50,000 (1)
- Risk
- Server failure
- P
- 0.1
- Loss
- ₹5,00,000
- RE (rank)
- ₹50,000 (4)
- Risk
- Vendor delay
- P
- 0.4
- Loss
- ₹1,50,000
- RE (rank)
- ₹60,000 (3)
Quality assurance vs quality control in project quality management: excerpt from page 33 of the MCA-215 notes
Excerpt from page 33 (Unit 3, sections 4 and 5), rewritten in English from the Hinglish original.
More QA activities
Beyond audits and reviews, quality assurance means defining standards and procedures such as coding standards and documentation templates, training the team on processes and tools, and checking that configuration management and change control are actually being followed.
PDCA cycle (Deming cycle) for continuous improvement
Plan: draw up an improvement plan. Do: try it on a small scale. Check: measure the results. Act: if it worked, make it the standard; if it did not, plan again. The loop then repeats, which is why PDCA is linked with continuous improvement.
Quality control (QC)
Quality control is product-oriented and detective. Specific project results are monitored and measured to see whether they meet the standards, and defects are identified and removed. The QC question is simple: is the thing we have built correct?
QC activities include testing at unit, integration, system and acceptance level; code and document inspection such as Fagan inspection; defect tracking with a bug log, severity and status; statistical sampling when testing everything is not possible; and acceptance decisions to accept, reject or rework.
| Basis | Quality assurance (QA) | Quality control (QC) |
|---|---|---|
| Focus | Process | Product |
| Nature | Preventive: stop defects arising | Detective and corrective: find and fix defects |
| Orientation | Proactive | Reactive |
| When | Across the life cycle, before and during development | After the product is built, in testing |
| Responsibility | The whole team or QA group | Testers or the QC team |
| Activities | Audits, process definition, reviews, training | Testing, inspection, defect tracking |
| Verification or validation | Verification: are we building it right? | Validation: are we building the right product? |
| Example | Setting coding standards and getting them followed | Testing the code to find bugs |
QA vs QC comparison (excerpt, page 33)
- Basis
- Focus
- Quality assurance (QA)
- Process
- Quality control (QC)
- Product
- Basis
- Nature
- Quality assurance (QA)
- Preventive: stop defects arising
- Quality control (QC)
- Detective and corrective: find and fix defects
- Basis
- Orientation
- Quality assurance (QA)
- Proactive
- Quality control (QC)
- Reactive
- Basis
- When
- Quality assurance (QA)
- Across the life cycle, before and during development
- Quality control (QC)
- After the product is built, in testing
- Basis
- Responsibility
- Quality assurance (QA)
- The whole team or QA group
- Quality control (QC)
- Testers or the QC team
- Basis
- Activities
- Quality assurance (QA)
- Audits, process definition, reviews, training
- Quality control (QC)
- Testing, inspection, defect tracking
- Basis
- Verification or validation
- Quality assurance (QA)
- Verification: are we building it right?
- Quality control (QC)
- Validation: are we building the right product?
- Basis
- Example
- Quality assurance (QA)
- Setting coding standards and getting them followed
- Quality control (QC)
- Testing the code to find bugs
Note: some books link QC with validation; in a comparison answer you can write both terms. Keep the table to at least four rows in a 12-mark answer, and end with one example of each.
How to write MCA-215 answers: CPM, PERT, COCOMO and EVM numericals plus twelve-mark theory answers
MCA-215 question papers mix two answer types. Units 2 and 4 reward numericals set out as a table, and Units 1 and 3 reward theory answers built around a diagram and a comparison table. Every unit question carries 12 marks, so a numerical needs the formula, the working table and a one-line conclusion, not just the final figure.
Slips the notes flag
- Adding PERT standard deviations instead of variances.
- Taking the maximum in the backward pass instead of the minimum LS.
- Putting KLOC into the COCOMO time formula instead of effort (D = c × Ed).
- Writing CV = AC − EV when it is EV − AC.
- Giving a bare list for "role of the project manager": every point needs one line of explanation.
Worked example: PERT probability (pages 19 to 20)
Six activities give three paths: A-D-F (15 weeks), A-C-E-F (14) and B-E-F (13).
- Expected time: te = (a + 4m + b) / 6. For B: (3 + 20 + 13) / 6 = 6.
- Critical path A-D-F, so Te = 15 weeks.
- Project variance = 0.444 + 0.444 + 0.111 = 1.0, so σp = 1.
- Z = (16 − 15) / 1 = 1.0, and P(Z ≤ 1.0) = 0.8413.
- Conclusion: an 84.13% chance of finishing in 16 weeks.
The notes add a line that lifts the answer: at 14 weeks, Z = −1 and the chance falls to 15.87%. That contrast shows the examiner you understand what σ means, and it costs one extra line. Box the final probability so it is easy to find.
Practise the same layout on GGSIPU MCA important questions.
MCA-215 exam corner: 48 short-answer and 32 long-answer expected questions by unit
| Unit | Short-answer | Long-answer | Solved numericals |
|---|---|---|---|
| Unit 1 | 12 | 8 | 0 |
| Unit 2 | 12 | 8 | 5 |
| Unit 3 | 12 | 8 | 0 |
| Unit 4 | 12 | 8 | 4 |
| Total | 48 | 32 | 9 |
Expected questions and solved numericals in the MCA-215 notes, by unit
- Unit
- Unit 1
- Short-answer
- 12
- Long-answer
- 8
- Solved numericals
- 0
- Unit
- Unit 2
- Short-answer
- 12
- Long-answer
- 8
- Solved numericals
- 5
- Unit
- Unit 3
- Short-answer
- 12
- Long-answer
- 8
- Solved numericals
- 0
- Unit
- Unit 4
- Short-answer
- 12
- Long-answer
- 8
- Solved numericals
- 4
- Unit
- Total
- Short-answer
- 48
- Long-answer
- 32
- Solved numericals
- 9
The MCA-215 notes list 48 short-answer and 32 long-answer expected questions across 4 units, plus 9 solved numericals.
One question per unit, with answer pointers:
- Unit 1: Explain the project life cycle with a neat diagram. How is it different from SDLC? Pointer (pages 7 to 8): five phases with the monitoring loop, each phase's output, then the comparison table.
- Unit 2: What is Earned Value Management? Solve a numerical. Pointer (pages 25 to 27): PV, EV, AC, BAC, the eight formulas, then the ₹10 lakh case.
- Unit 3: Discuss quality standards: ISO 9001, CMMI and Six Sigma. Pointer (pages 34 to 35): ISO principles, CMMI levels, DMAIC.
- Unit 4: What is software configuration management? Explain its activities and change control process. Pointer (page 51): baseline, IEEE 828 activities, CCB flow.
More practice sits in the MCA-215 important questions.
MCA-215 and the GGSIPU MCA Sem 3 papers it connects to
Paired lab: MCA-265 Software Project Management Lab (1 credit), listed on the GGSIPU MCA syllabus page; there is no separate lab notes book for it yet.
Its outcomes map onto the theory: CO1 (proposal) uses Unit 1, CO2 (schedule and budget) and CO4 (resource estimates) use Unit 2's CPM, COCOMO and EVM, CO3 (risk) uses Unit 4, and CO5 needs all four units.
- MCA-269 Minor Project-III: the Gantt chart and risk register fit straight into a project report.
- MCA-239 Software Quality Management (Core Elective-III): overlaps Unit 3 on CMMI, ISO 9001 and QC tools.
The pre-requisite, software engineering concepts, comes from MCA-104 Object Oriented Software Engineering in Semester 2. The core papers alongside are MCA-201 Design and Analysis of Algorithms and MCA-203 Artificial Intelligence and Machine Learning.
Who writes and checks the MCA-215 SPM 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. Author profile
- Ritik Rawat, subject reviewer: Senior Full Stack Developer, Unnati Educations; B.Tech.
These MCA-215 Software Project Management IPU notes are mapped to the MCA scheme approved by the USIC&T Board of Studies on 28 July 2025. The 2026-27 edition has 55 pages, with a Common Mistakes box and a Quick Revision sheet in every unit. Last updated 14 October 2026, under our editorial policy.
The same team prepares GGSIPU important questions for every course.
Do the MCA-215 notes cover the full GGSIPU syllabus?
Yes. Every topic in the four official units has its own section in the notes, and the unit check found no gaps.
| Official unit | Official topics | Where in the notes | Status |
|---|---|---|---|
| Unit I | Introduction, scope, life cycle, manager's role, tools; planning: objectives, demand, proposal, requirements, legal issues, budget, teams, usability; MS Project | Sections 1 to 12, pages 5 to 15 | Covered |
| Unit II | Scheduling: network, critical path, PERT, Gantt; cost: metrics, estimation, COCOMO I and II, earned value, budget control | Sections 1 to 12, pages 17 to 28 | Covered |
| Unit III | Quality: stages, planning, QA, QC, standards, tools; HR: CRM, key terms, staffing, team development, performance reporting | Sections 1 to 13, pages 31 to 41 | Covered |
| Unit IV | Risk: sources, identification, quantification, response; procurement; monitoring, configuration management, metrics, closure | Sections 1 to 13, pages 44 to 53 | Covered |
MCA-215 official syllabus topics mapped to the notes
- Official unit
- Unit I
- Official topics
- Introduction, scope, life cycle, manager's role, tools; planning: objectives, demand, proposal, requirements, legal issues, budget, teams, usability; MS Project
- Where in the notes
- Sections 1 to 12, pages 5 to 15
- Status
- Covered
- Official unit
- Unit II
- Official topics
- Scheduling: network, critical path, PERT, Gantt; cost: metrics, estimation, COCOMO I and II, earned value, budget control
- Where in the notes
- Sections 1 to 12, pages 17 to 28
- Status
- Covered
- Official unit
- Unit III
- Official topics
- Quality: stages, planning, QA, QC, standards, tools; HR: CRM, key terms, staffing, team development, performance reporting
- Where in the notes
- Sections 1 to 13, pages 31 to 41
- Status
- Covered
- Official unit
- Unit IV
- Official topics
- Risk: sources, identification, quantification, response; procurement; monitoring, configuration management, metrics, closure
- Where in the notes
- Sections 1 to 13, pages 44 to 53
- Status
- Covered
Official source: MCA Scheme of Examination and Detailed Syllabus, affiliated institutes, 2025-26 onwards · Ordinance 11 (examinations and results)
If you are comparing GGSIPU MCA Sem 3 Software Project Management notes, check them against this table. Every course in GGSIPU notes is mapped to its official PDF the same way.
MCA-215 SPM notes FAQs
How do I get the full MCA-215 notes?
Order them on WhatsApp at 9899436384 with the "Get Full Notes" button on this page. The full MCA-215 notes come as a printed book only and are not available as a PDF. Delivery takes 5 to 7 days at most, depending on your location. The sample PDF at the top shows seven pages of the book first.
What is the passing mark for MCA-215 Software Project Management?
MCA-215 has a 60-mark end-term paper: a 12-mark compulsory Q1 and four 12-mark unit questions. The MCA scheme of examination states pass marks as 40%, which is 40 out of 100, for every paper. The official PDF prints no separate internal split. For end-term minimums, re-appear rules and results, see GGSIPU Ordinance 11 on ipu.ac.in.
Is MCA-215 compulsory in MCA Semester 3?
No. MCA-215 is one of 11 options in Core Elective-II, and you choose one. The scheme also says an elective needs at least 20 students for classes. With fewer, it may still be offered, but students complete it through a MOOC on SWAYAM or a similar platform, with prior approval, and then sit the institution's own evaluation. In that case, practise Unit 1's MS Project or ProjectLibre steps on your own.
Which MCA-215 unit has the most numericals?
Unit 2 has the most, with 5 solved numericals: CPM, PERT probability, Basic COCOMO in all three modes, COCOMO II and a full earned value analysis. Unit 4 follows with 4: risk exposure with ranking, an EMV decision tree, make-or-buy breakeven and defect metrics. Units 1 and 3 are theory units, with one quick example each on ROI and DPMO.
Are the MCA-215 notes in English or Hindi?
The MCA-215 notes are in simple Hinglish, which is Hindi in Roman script mixed with English, so the explanations read like a teacher talking. Every formula, table, definition, diagram and expected question is in English, so you can write your answers in English straight from them. The excerpt on this page shows the content rewritten in English.
Is there a lab paper linked to MCA-215?
Yes. Students who choose MCA-215 take MCA-265, the Lab based on Core Elective-II, which for this elective is the 1-credit Software Project Management Lab. Its five course outcomes cover a proposal, scheduling and budget, risk, resource estimates and a complete project. The official PDF gives no practical list, and this book covers the theory paper.
Get the full MCA-215 Software Project Management Notes on WhatsApp
What is in the full MCA-215 notes book, by unit
- Part
- Cover and index
- Pages
- 1 to 3 (3)
- Sections
- -
- Solved numericals
- -
- Part
- Unit 1
- Pages
- 4 to 15 (12)
- Sections
- 12
- Solved numericals
- 0
- Part
- Unit 2
- Pages
- 16 to 29 (14)
- Sections
- 12
- Solved numericals
- 5
- Part
- Unit 3
- Pages
- 30 to 42 (13)
- Sections
- 13
- Solved numericals
- 0
- Part
- Unit 4
- Pages
- 43 to 55 (13)
- Sections
- 13
- Solved numericals
- 4
55 pages including cover and index: 50 sections, 80 expected questions and a Unit 2 formula sheet.
Format: printed book only; not available as a PDF. Delivery: within 5 to 7 days at most; the exact time may vary with your location.
Order the full MCA-215 Software Project Management Notes book on WhatsApp (4 units, 55 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.