Software Project Management (BSc CSIT, CSC466): the questions likely to come
26 analyzed questions from 7 past papers (2074-2081), grouped by syllabus unit — each with its probability, how often it's been asked, and where to study the answer.
What is software configuration management? Explain its importance, the configuration management process, and discuss software quality management and quality plans.
Software Configuration Management (SCM)
Software Configuration Management is the discipline of identifying, organizing and controlling changes to the artefacts (code, documents, designs, data) produced and maintained during a software project, so that the integrity and traceability of the product are maintained throughout its life cycle.
Importance
- Controls and tracks changes, preventing uncontrolled / conflicting changes to artefacts.
- Maintains the integrity and consistency of all deliverables.
- Supports team coordination by managing concurrent work on shared items.
- Enables reproducibility – any released version (baseline) can be rebuilt.
- Provides traceability and auditability of who changed what, when and why.
Configuration Management Process
- Configuration Identification – identify and label the configuration items (CIs) (modules, documents, libraries) and define baselines.
- Configuration / Change Control – manage change requests through a Change Control Board (CCB): raise, evaluate impact, approve/reject, implement and verify changes.
- Configuration Status Accounting – record and report the status of CIs and change requests (what version is current, which changes are pending/done).
- Configuration Audits (Verification & Audit) – functional and physical audits confirm that the built product conforms to its requirements and recorded configuration.
- Release Management & Version Control – manage versions, branches and releases (often using tools such as Git/SVN).
Software Quality Management
Quality management ensures that the software meets its specified requirements and is fit for purpose. It has three parts:
- Quality Assurance (QA) – establishing the organizational procedures and standards that lead to high-quality software (process focused).
- Quality Planning – selecting the standards and procedures appropriate to a particular project and defining the quality targets.
- Quality Control – checking that processes and standards are actually followed (reviews, inspections, testing).
Software Quality Plan
A quality plan defines how quality will be achieved for a specific project. Its contents typically include:
- Product introduction & plans – the product, its market, release and quality milestones.
- Process descriptions – the development and quality processes to be used.
- Quality goals – the key quality attributes (reliability, usability, maintainability, etc.) and how they are measured.
- Risks and risk management – quality-related risks and their mitigation.
- Standards, reviews, and metrics to be applied.
Quality management and SCM are complementary: SCM keeps the artefacts under control while quality management ensures those artefacts meet the required standards.
Resource Allocation, Monitoring and Control
What is software configuration management? Explain its importance, the configuration management process, and discuss software quality management and quality plans.
Explain project monitoring and control. Discuss earned value analysis (EVA), including the computation of BCWS, BCWP, ACWP, schedule variance and cost variance with an example.
Explain earned value analysis. Define schedule variance and cost variance.
What is project scheduling? Explain the use of a Gantt chart.
What is software configuration management? Why is it important?
Explain the different types of contracts used in software project acquisition.
Explain the techniques used for monitoring the progress of a software project.
What is resource allocation? Explain resource smoothing and resource leveling.
Write short notes on change management and change control in software projects.
Sit a probable paper
A full mock exam built from the most likely questions, mirroring the real paper's structure. Every slot is a real past question.
Most Probable Paper
Mirrors the real structure · 60 marks · based on 7 past papers
- 1.[10 marks]
What is software configuration management? Explain its importance, the configuration management process, and discuss software quality management and quality plans.
This question has recurred in 3 of 7 years; so far only in internal assessments, not the board; and its topic (Resource Allocation, Monitoring and Control) appears in 100% of years.
- 2.[10 marks]
Explain project monitoring and control. Discuss earned value analysis (EVA), including the computation of BCWS, BCWP, ACWP, schedule variance and cost variance with an example.
This question has recurred in 3 of 7 years; so far only in internal assessments, not the board; and its topic (Resource Allocation, Monitoring and Control) appears in 100% of years.
- 3.[10 marks]
What is risk management in software projects? Explain the risk management framework (identification, assessment, planning and control) and discuss techniques for evaluating risks to the schedule using PERT and Z-values.
This question has recurred in 3 of 7 years; so far only in internal assessments, not the board; and its topic (Activity Planning and Risk Management) appears in 86% of years.
- 1.[5 marks]
Explain earned value analysis. Define schedule variance and cost variance.
This question has recurred in 4 of 7 years; so far only in internal assessments, not the board; and its topic (Resource Allocation, Monitoring and Control) appears in 100% of years.
- 2.[5 marks]
What is project scheduling? Explain the use of a Gantt chart.
This question has recurred in 4 of 7 years; so far only in internal assessments, not the board; and its topic (Resource Allocation, Monitoring and Control) appears in 100% of years.
- 3.[5 marks]
What is software configuration management? Why is it important?
This question has recurred in 4 of 7 years; so far only in internal assessments, not the board; and its topic (Resource Allocation, Monitoring and Control) appears in 100% of years.
- 4.[5 marks]
Explain the different types of contracts used in software project acquisition.
This question has recurred in 4 of 7 years; so far only in internal assessments, not the board; and its topic (Resource Allocation, Monitoring and Control) appears in 100% of years.
- 5.[5 marks]
What is the Critical Path Method (CPM)? How is the critical path determined?
This question has recurred in 4 of 7 years; so far only in internal assessments, not the board; and its topic (Activity Planning and Risk Management) appears in 86% of years.
- 6.[5 marks]
Explain the PERT technique and the three-point estimation of activity duration.
This question has recurred in 4 of 7 years; so far only in internal assessments, not the board; and its topic (Activity Planning and Risk Management) appears in 86% of years.
- 7.[5 marks]
What is risk? Explain the steps of the risk management process.
This question has recurred in 4 of 7 years; so far only in internal assessments, not the board; and its topic (Activity Planning and Risk Management) appears in 86% of years.
- 8.[5 marks]
Explain the basic COCOMO model with its effort estimation equation.
This question has recurred in 4 of 7 years; so far only in internal assessments, not the board; and its topic (Software Effort Estimation) appears in 100% of years.
- 9.[5 marks]
What is the function point analysis technique for software size estimation?
This question has recurred in 4 of 7 years; so far only in internal assessments, not the board; and its topic (Software Effort Estimation) appears in 100% of years.
Behind the numbers
The raw evidence the predictions are computed from: marks per unit per year, syllabus weights, trends, and coverage.
Show the heatmap, topic table and coverage analysis
The receipt: marks per unit, per year
Each row is a syllabus unit, each column an exam year, each cell the marks that unit earned that year. Click any cell to see the actual questions behind it.
| # | Syllabus unit | Probability | Appeared | Avg marks | Syllabus weight | Exam vs syllabus | Trend | Questions |
|---|---|---|---|---|---|---|---|---|
| 1 | U6Resource Allocation, Monitoring and Control | Very likely100% | 26.4 | 18%8 lecture hrs | Over-examinedexam 35% · syllabus 18% | Steady | 9 recurring9 total | |
| 2 | U5Activity Planning and Risk Management | Very likely86% | 20 | 20%9 lecture hrs | Balancedexam 23% · syllabus 20% | Steady | 5 recurring5 total | |
| 3 | U4Software Effort Estimation | Very likely100% | 12.1 | 18%8 lecture hrs | Balancedexam 16% · syllabus 18% | Steady | 4 recurring4 total | |
| 4 | U1Introduction to Software Project Management | Very likely86% | 11.7 | 13%6 lecture hrs | Balancedexam 13% · syllabus 13% | Rising | 4 recurring4 total | |
| 5 | U3An Overview of Project Planning and Selection of Project Approach | Likely57% | 16.2 | 18%8 lecture hrs | Under-examinedexam 12% · syllabus 18% | Steady | 3 recurring4 total | |
| 6 | U2Project Evaluation and Programme Management | Occasional0% | 0 | 13%6 lecture hrs | Under-examinedexam 0% · syllabus 13% | Steady | None |
Study smart, not hard
Drag the slider: studying the top 4 units in priority order covers ~88% of all observed marks.
- ~80% line
Lecture time vs exam marks
Where the exam pays more than the curriculum spends: ● lectures vs ● exam marks, as a share of the whole course. A long teal-leading bar = high-yield unit.