Software Engineering Assessment 2 — Questions and Answers
Question 1: Which metric measures the average number of defects found per lines of code during a code review?
- Defect density (Correct answer)
- Code churn
- Cyclomatic complexity
- Test coverage
Correct answer: Defect density
Defect density is calculated as the number of defects divided by the size of the software (usually per KLOC).
Question 2: In software assessment, what does a 'baseline' primarily serve as?
- A performance benchmark for future comparisons (Correct answer)
- A list of all known defects
- The initial project cost estimate
- The final version of the software
Correct answer: A performance benchmark for future comparisons
A baseline is an established reference point used to measure and compare future changes or performance.
Question 3: A team uses pair programming and finds fewer post-release defects. Which assessment dimension does this best illustrate?
- Process quality (Correct answer)
- Product quality
- Project velocity
- Team morale
Correct answer: Process quality
Pair programming is a process practice, and its impact on defect rates reflects process quality assessment.
Question 4: Static analysis tools assess software WITHOUT doing which of the following?
- Executing the program (Correct answer)
- Parsing the source code
- Checking for coding standards
- Detecting potential null pointer dereferences
Correct answer: Executing the program
Static analysis examines code structure and patterns without running the program, unlike dynamic analysis.
Question 5: Which CMMI maturity level indicates that processes are documented, standardized, and consistently followed across the organization?
- Level 3 – Defined (Correct answer)
- Level 2 – Managed
- Level 4 – Quantitatively Managed
- Level 5 – Optimizing
Correct answer: Level 3 – Defined
CMMI Level 3 (Defined) means processes are proactively documented and tailored from organizational standards.
Question 6: During a software capability assessment, evaluators discover that a team's estimates consistently run 40% over actual effort. What root cause category does this most likely indicate?
- Estimation process weakness (Correct answer)
- Insufficient testing
- Poor version control
- Inadequate requirements
Correct answer: Estimation process weakness
Systematic over-estimation points to a flawed or immature estimation process rather than individual technical issues.
Question 7: Which assessment technique involves systematically walking through code with a group of peers to identify defects?
- Formal inspection (Correct answer)
- Unit testing
- Load testing
- Regression testing
Correct answer: Formal inspection
A formal inspection (e.g., Fagan inspection) is a structured peer review where a team walks through code to find defects.
Software Engineering Assessment 2
Which metric measures the average number of defects found per lines of code during a code review?