1. . Software metrics are:
(A) CPU scheduling method
(B) Only coding lines
(C) Quantitative measures used to assess software processes, products, and projects
(D) Memory allocation method
2. . The main goal of software metrics is:
(A) Allocate memory only
(B) Improve quality, productivity, and maintainability of software
(C) CPU optimization
(D) File deletion
3. . Metrics can be classified into:
(A) File metrics only
(B) CPU metrics only
(C) Memory metrics only
(D) Product metrics, process metrics, and project metrics
4. . Product metrics measure:
(A) Characteristics of software products, such as size, complexity, and quality
(B) CPU speed only
(C) Memory usage only
(D) File management only
5. . Process metrics measure:
(A) Product size only
(B) Effectiveness and efficiency of software development and maintenance processes
(C) CPU usage only
(D) Memory allocation only
6. . Project metrics measure:
(A) File management only
(B) CPU only
(C) Memory allocation only
(D) Attributes related to project management like cost, effort, and schedule
7. . Lines of Code (LOC) is an example of:
(A) Product metric
(B) Process metric
(C) Project metric
(D) CPU metric
8. . Cyclomatic complexity measures:
(A) CPU speed
(B) The complexity of a program based on the number of independent paths
(C) Memory usage
(D) File size
9. . Function points measure:
(A) Memory allocation
(B) CPU usage
(C) Software functionality delivered to the user
(D) File deletion
10. . Defect density metric measures:
(A) CPU speed
(B) Number of defects per unit size of the software
(C) Memory allocation
(D) File size
11. . Effort metric measures:
(A) The total person-hours required to develop or maintain software
(B) CPU speed
(C) Memory usage
(D) File management
12. . Schedule metric measures:
(A) The time required to complete software development or maintenance activities
(B) Memory allocation
(C) CPU scheduling
(D) File management
13. . Quality metric measures:
(A) CPU speed
(B) Attributes like reliability, maintainability, and usability of software
(C) Memory allocation
(D) File size
14. . Rework metric measures:
(A) Effort spent in correcting defects after initial development
(B) CPU optimization
(C) Memory allocation
(D) File deletion
15. . Productivity metric measures:
(A) CPU speed
(B) Software output per unit effort (e.g., LOC per person-month)
(C) Memory usage
(D) File management
16. . Metrics should be:
(A) Measurable, objective, and actionable
(B) Only subjective
(C) CPU-based only
(D) Memory-based only
17. . Software measurement helps in:
(A) CPU scheduling only
(B) Project planning, monitoring, quality improvement, and decision-making
(C) Memory allocation only
(D) File management only
18. . Early defect detection metrics help in:
(A) CPU optimization only
(B) Reducing cost and effort for fixing defects
(C) Memory allocation only
(D) File deletion only
19. . Risk metrics measure:
(A) Potential risks in software projects to facilitate mitigation strategies
(B) CPU speed
(C) Memory usage
(D) File size
20. . The ultimate goal of software metrics & measurement is:
(A) Improve software quality, process efficiency, and project management effectiveness
(B) Only allocate memory
(C) Only optimize CPU
(D) Delete files automatically