This set of Software Project Management MCQ covers advanced concepts of Software Project Management, including COCOMO II, PERT analysis, Earned Value Management (EVM), Function Point Analysis, Halstead metrics, Cleanroom Software Engineering, CMMI, Software Configuration Management, and project estimation models. Useful for GATE, UGC NET, IBPS IT Officer, and university semester examinations.
Topic: Software Engineering (Software Project Management) | Set: 3
Difficulty: Hard | Total Questions: 15
Software Project Management MCQs
Q1. In a critical path analysis network diagram, how is the Total Float (TF) mathematically calculated?
A. Late Start (LS) – Early Start (ES)
B. Early Finish (EF) – Early Start (ES)
C. Late Finish (LF) – Late Start (LS)
D. Early Start (ES) – Late Finish (LF)
View Answer & Explanation
Answer: A
Explanation: Total Float represents the allowable delay without affecting the final project completion date and is calculated as LS – ES.
Q2. Under COCOMO II, what is the core difference between scale factors and cost drivers?
A. Scale factors apply exponentially while cost drivers apply linearly
B. Scale factors evaluate external constraints only
C. Scale factors decrease over time
D. Scale factors are qualitative only
View Answer & Explanation
Answer: A
Explanation: Scale factors affect the exponent of the effort equation, while cost drivers adjust the estimated effort multiplicatively.
Q3. In Function Point analysis, which statement best defines an External Output (EO)?
A. Data retrieval only
B. Input process updating internal files
C. Output containing calculations or derived processing
D. Hardware configuration block
View Answer & Explanation
Answer: C
Explanation: External Outputs involve processing logic, calculations, or derived data before presenting output outside the system boundary.
Q4. If BAC = $200,000 and CPI = 0.80, what is the Estimate at Completion (EAC)?
A. $160,000
B. $250,000
C. $240,000
D. $220,000
View Answer & Explanation
Answer: B
Explanation: EAC = BAC / CPI = 200,000 / 0.80 = $250,000.
Q5. Halstead’s Software Science metrics are primarily based on which parameters?
A. File directories and folders
B. Unique operators, operands, and total occurrences
C. Cyclomatic complexity
D. Function entry points
View Answer & Explanation
Answer: B
Explanation: Halstead metrics analyze operators and operands to calculate software vocabulary, length, and volume.
Q6. If the standard deviation of a PERT task is 1.5 days, what is its variance?
A. 3.00
B. 2.25
C. 1.22
D. 0.75
View Answer & Explanation
Answer: B
Explanation: Variance = σ² = 1.5 × 1.5 = 2.25.
Q7. How is the overall project standard deviation of a critical path calculated?
A. Sum all standard deviations directly
B. Average all standard deviations
C. Square root of the sum of variances
D. Multiply highest variance by path length
View Answer & Explanation
Answer: C
Explanation: Variances are added for independent activities, and the square root gives the combined standard deviation.
Q8. Which philosophy underpins Cleanroom Software Engineering?
A. Heavy bug fixing during testing
B. Statistical control and formal verification
C. Rapid prototyping cycles
D. Ignoring documentation
View Answer & Explanation
Answer: B
Explanation: Cleanroom engineering emphasizes defect prevention through formal verification and statistical quality control.
Q9. The Putnam Estimation Model shows a non-linear relationship between effort and which parameter?
A. Database storage
B. Development time raised to the 4th or 5th power
C. Server clusters
D. Salary structure
View Answer & Explanation
Answer: B
Explanation: The Putnam model demonstrates that compressing development time requires exponentially higher effort.
Q10. At CMMI Level 4, how is process performance primarily evaluated?
A. Qualitative reports
B. Statistical methods and control charts
C. Flexible process changes
D. Revenue tracking
View Answer & Explanation
Answer: B
Explanation: Level 4 organizations use quantitative analysis and statistical controls for predictable process performance.
Q11. What is the primary purpose of an Ishikawa (Fishbone) diagram?
A. Sprint tracking
B. Root cause analysis
C. LOC estimation
D. Security hierarchy planning
View Answer & Explanation
Answer: B
Explanation: Fishbone diagrams systematically identify possible root causes of defects or project failures.
Q12. What problem occurs when LOC is used to compare Python and Assembly productivity?
A. Python appears less productive
B. High-level languages are unfairly penalized
C. Assembly cannot be counted
D. Testing is ignored
View Answer & Explanation
Answer: B
Explanation: High-level languages express more functionality with fewer lines, making LOC comparisons misleading.
Q13. In SCM, what concept allows isolated development away from the main production line?
A. Baselining
B. Branching
C. Spilling
D. Diffing
View Answer & Explanation
Answer: B
Explanation: Branching creates an isolated development path without affecting the stable production branch.
Q14. What metric assesses Requirements Volatility?
A. Reading speed of specifications
B. Ratio of changed requirements to baseline requirements
C. Requirements per engineer
D. SRS document word count
View Answer & Explanation
Answer: B
Explanation: Requirements volatility measures how frequently project requirements change relative to the original baseline.
Q15. During a Formal Technical Review (FTR), what does Review Density measure?
A. Number of reviewers per room
B. Defects identified per unit size reviewed
C. Comment-to-code ratio
D. Presentation reading speed
View Answer & Explanation
Answer: B
Explanation: Review Density measures review effectiveness by tracking defects found relative to artifact size.
Conclusion
These Software Project Management MCQ questions covered advanced concepts such as COCOMO II, Function Point Analysis, Halstead metrics, PERT calculations, Cleanroom Software Engineering, CMMI maturity levels, and Earned Value Management.
Practicing these advanced concepts is highly useful for GATE CS, UGC NET, IBPS IT Officer, software engineering interviews, and university semester examinations.
For better understanding of theories and concepts, please refer Software Project Management Concepts.