Q1. Software metrics are:
(A) Quantitative measures used to assess software quality, performance, and productivity
(B) Only coding lines
(C) UI screens only
(D) Hardware specifications
Answer: (A) Quantitative measures used to assess software quality, performance, and productivity
Q2. Main purpose of software metrics is:
(A) Improve software quality, manage projects, and measure productivity
(B) Only coding tasks
(C) UI only
(D) Hardware only
Answer: (A) Improve software quality, manage projects, and measure productivity
Q3. Software measurement involves:
(A) Assigning numeric values to software attributes
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Assigning numeric values to software attributes
Q4. Product metrics measure:
(A) Characteristics of the software product such as size, complexity, and quality
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Characteristics of the software product such as size, complexity, and quality
Q5. Process metrics measure:
(A) Attributes of software development process such as productivity and defect density
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Attributes of software development process such as productivity and defect density
Q6. Project metrics measure:
(A) Progress, schedule adherence, cost, and resource utilization
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Progress, schedule adherence, cost, and resource utilization
Q7. Lines of Code (LOC) metric measures:
(A) Size of software by counting the number of source lines
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Size of software by counting the number of source lines
Q8. Function points (FP) measure:
(A) Size of software based on functionality delivered to users
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Size of software based on functionality delivered to users
Q9. Cyclomatic complexity measures:
(A) Complexity of program based on number of independent paths
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Complexity of program based on number of independent paths
Q10. Halstead metrics measure:
(A) Software complexity based on operators and operands
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Software complexity based on operators and operands
Q11. Defect density is:
(A) Number of defects per unit size of software
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Number of defects per unit size of software
Q12. Maintainability index measures:
(A) Ease of maintaining and modifying software
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Ease of maintaining and modifying software
Q13. Rework effort metric measures:
(A) Effort required to correct defects in software
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Effort required to correct defects in software
Q14. Productivity metric measures:
(A) Software output per unit of effort
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Software output per unit of effort
Q15. Schedule adherence metric measures:
(A) Extent to which project milestones are met on time
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Extent to which project milestones are met on time
Q16. Cost variance metric measures:
(A) Difference between planned and actual project costs
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Difference between planned and actual project costs
Q17. Software reliability metrics include:
(A) Mean time to failure (MTTF) and defect density
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Mean time to failure (MTTF) and defect density
Q18. Mean Time To Failure (MTTF) measures:
(A) Average operational time before software fails
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Average operational time before software fails
Q19. Availability metric measures:
(A) Proportion of time software is operational and accessible
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Proportion of time software is operational and accessible
Q20. Response time metric measures:
(A) Time taken by system to respond to user request
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Time taken by system to respond to user request
Q21. Software usability metrics include:
(A) User satisfaction, error rate, and learnability
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) User satisfaction, error rate, and learnability
Q22. Error detection efficiency measures:
(A) Proportion of errors detected during testing
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Proportion of errors detected during testing
Q23. Mean time to repair (MTTR) measures:
(A) Average time to fix defects after detection
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Average time to fix defects after detection
Q24. Metrics can be classified as:
(A) Product, process, and project metrics
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Product, process, and project metrics
Q25. Size-oriented metrics include:
(A) Lines of code (LOC) and function points (FP)
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Lines of code (LOC) and function points (FP)
Q26. Complexity-oriented metrics include:
(A) Cyclomatic complexity, Halstead metrics
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Cyclomatic complexity, Halstead metrics
Q27. Defect-related metrics include:
(A) Defect density, mean time to failure, defect removal efficiency
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Defect density, mean time to failure, defect removal efficiency
Q28. Process metrics help in:
(A) Monitoring development productivity and efficiency
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Monitoring development productivity and efficiency
Q29. Project metrics help in:
(A) Tracking schedule, cost, and progress of software projects
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Tracking schedule, cost, and progress of software projects
Q30. Software quality metrics focus on:
(A) Functionality, reliability, usability, efficiency, maintainability
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Functionality, reliability, usability, efficiency, maintainability
Q31. Software defect metric helps to:
(A) Identify high-risk modules and improve quality
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Identify high-risk modules and improve quality
Q32. Metrics for maintainability include:
(A) Cyclomatic complexity, LOC, module coupling
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Cyclomatic complexity, LOC, module coupling
Q33. Software reliability is measured by:
(A) Mean time to failure (MTTF) and failure rate
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Mean time to failure (MTTF) and failure rate
Q34. Software productivity metric can be:
(A) LOC per person-month or FP per person-month
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) LOC per person-month or FP per person-month
Q35. Defect removal efficiency (DRE) measures:
(A) Percentage of defects detected and removed before release
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Percentage of defects detected and removed before release
Q36. Metrics support:
(A) Software estimation, process improvement, project control
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Software estimation, process improvement, project control
Q37. Reliability metrics can be categorized as:
(A) Failure metrics and defect metrics
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Failure metrics and defect metrics
Q38. Mean time between failures (MTBF) measures:
(A) Average time between two consecutive failures
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Average time between two consecutive failures
Q39. Software quality factor “efficiency” measures:
(A) Resource utilization and response time
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Resource utilization and response time
Q40. Software quality factor “usability” measures:
(A) Learnability, user satisfaction, and error rate
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Learnability, user satisfaction, and error rate
Q41. Software quality factor “maintainability” measures:
(A) Ease of modifying and correcting software
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Ease of modifying and correcting software
Q42. Software quality factor “reliability” measures:
(A) Software ability to perform without failure
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Software ability to perform without failure
Q43. Size metric is important for:
(A) Estimation of effort, cost, and schedule
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Estimation of effort, cost, and schedule
Q44. Cyclomatic complexity formula is:
(A) V(G) = E – N + 2P
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) V(G) = E – N + 2P
Q45. Halstead effort metric measures:
(A) Estimated mental effort required to develop software
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Estimated mental effort required to develop software
Q46. Function point metric counts:
(A) Inputs, outputs, inquiries, files, and interfaces
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Inputs, outputs, inquiries, files, and interfaces
Q47. LOC metric drawback is:
(A) Does not measure software complexity or quality
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Does not measure software complexity or quality
Q48. Metrics help in risk management by:
(A) Identifying modules prone to defects or delays
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Identifying modules prone to defects or delays
Q49. Early defect detection can be measured using:
(A) Defect density and defect removal efficiency
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Defect density and defect removal efficiency
Q50. Metrics provide feedback for:
(A) Process improvement and software quality enhancement
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Process improvement and software quality enhancementQ51. Complexity metrics help in:
(A) Identifying complex modules that may cause maintenance problems
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Identifying complex modules that may cause maintenance problems
Q52. Coupling metric measures:
(A) Degree of interdependence between modules
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Degree of interdependence between modules
Q53. Cohesion metric measures:
(A) Degree to which elements within a module belong together
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Degree to which elements within a module belong together
Q54. Metrics help in software estimation by:
(A) Providing historical data for effort and cost prediction
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Providing historical data for effort and cost prediction
Q55. Response time metric is critical for:
(A) Real-time and interactive systems
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Real-time and interactive systems
Q56. Reliability metric helps in:
(A) Predicting software failures and planning maintenance
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Predicting software failures and planning maintenance
Q57. Defect removal efficiency (DRE) formula is:
(A) DRE = (Defects found before release / Total defects) × 100
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) DRE = (Defects found before release / Total defects) × 100
Q58. Maintainability metrics include:
(A) Cyclomatic complexity, code modularity, and documentation quality
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Cyclomatic complexity, code modularity, and documentation quality
Q59. Software productivity can be measured in:
(A) LOC per person-month or FP per person-month
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) LOC per person-month or FP per person-month
Q60. Metrics for software process improvement include:
(A) Defect trends, development time, and resource utilization
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Defect trends, development time, and resource utilization
Q61. Software performance metrics measure:
(A) Speed, response time, throughput, and resource utilization
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Speed, response time, throughput, and resource utilization
Q62. Metrics support benchmarking by:
(A) Comparing software quality and productivity with industry standards
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Comparing software quality and productivity with industry standards
Q63. Error rate metric is defined as:
(A) Number of errors per unit of software size or time
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Number of errors per unit of software size or time
Q64. Software complexity affects:
(A) Maintainability, reliability, and testing effort
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Maintainability, reliability, and testing effort
Q65. Metrics help in decision-making by:
(A) Providing objective data for project planning and control
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Providing objective data for project planning and control
Q66. Quality metrics focus on:
(A) Correctness, reliability, maintainability, and usability
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Correctness, reliability, maintainability, and usability
Q67. Code churn metric measures:
(A) Frequency of code changes in a module over time
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Frequency of code changes in a module over time
Q68. Metrics in testing phase include:
(A) Defect density, test coverage, and test execution rate
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Defect density, test coverage, and test execution rate
Q69. Test coverage metric measures:
(A) Percentage of code or requirements exercised by tests
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Percentage of code or requirements exercised by tests
Q70. Metrics help in project risk management by:
(A) Identifying high-risk areas based on complexity and defect trends
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Identifying high-risk areas based on complexity and defect trends
Q71. Metrics can be classified as objective or subjective:
(A) Objective: numeric data, Subjective: opinions or ratings
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Objective: numeric data, Subjective: opinions or ratings
Q72. Function point analysis helps in:
(A) Measuring software size based on user requirements
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Measuring software size based on user requirements
Q73. Complexity metrics are useful for:
(A) Predicting maintenance effort and defect-prone modules
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Predicting maintenance effort and defect-prone modules
Q74. Code coverage metrics measure:
(A) Percentage of code executed by test cases
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Percentage of code executed by test cases
Q75. Metrics help in continuous improvement by:
(A) Identifying weaknesses and tracking improvements over time
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Identifying weaknesses and tracking improvements over time
Q76. Metrics help in estimating project effort by:
(A) Using historical data and size metrics like LOC or FP
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Using historical data and size metrics like LOC or FP
Q77. Defect trend metric shows:
(A) Pattern of defect discovery over time
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Pattern of defect discovery over time
Q78. Mean time to detect (MTTD) measures:
(A) Average time to identify a defect after it occurs
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Average time to identify a defect after it occurs
Q79. Mean time to repair (MTTR) is important for:
(A) Measuring maintenance efficiency
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Measuring maintenance efficiency
Q80. Software metric can be used for:
(A) Project monitoring, quality assessment, and process improvement
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Project monitoring, quality assessment, and process improvement
Q81. LOC metric is limited because:
(A) It does not reflect complexity or quality
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) It does not reflect complexity or quality
Q82. Cyclomatic complexity is calculated using:
(A) V(G) = E – N + 2P
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) V(G) = E – N + 2P
Q83. Metrics help managers by:
(A) Providing objective data for planning, control, and improvement
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Providing objective data for planning, control, and improvement
Q84. High defect density indicates:
(A) Low software quality and high risk
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Low software quality and high risk
Q85. Metrics can be collected manually or:
(A) Using automated tools
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Using automated tools
Q86. Metrics improve testing by:
(A) Identifying defect-prone areas and coverage gaps
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Identifying defect-prone areas and coverage gaps
Q87. Metrics provide feedback to:
(A) Developers, testers, and project managers
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Developers, testers, and project managers
Q88. Process improvement metrics track:
(A) Productivity, defect trends, and cycle time
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Productivity, defect trends, and cycle time
Q89. Software quality is measured by:
(A) Reliability, maintainability, efficiency, usability, and portability
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Reliability, maintainability, efficiency, usability, and portability
Q90. Software metrics help in benchmarking by:
(A) Comparing performance and quality against standards or past projects
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Comparing performance and quality against standards or past projects
Q91. Code modularity metric measures:
(A) Degree to which code is divided into independent modules
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Degree to which code is divided into independent modules
Q92. Metrics aid in early defect detection by:
(A) Highlighting complex or error-prone modules
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Highlighting complex or error-prone modules
Q93. Metrics can be:
(A) Leading (predictive) or lagging (historical) indicators
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Leading (predictive) or lagging (historical) indicators
Q94. Software maintainability is affected by:
(A) Code complexity, documentation, and modularity
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Code complexity, documentation, and modularity
Q95. Metrics for defect analysis include:
(A) Defect density, severity distribution, and defect trends
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Defect density, severity distribution, and defect trends
Q96. Metrics help in estimating testing effort by:
(A) Using historical defect data and module complexity
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Using historical defect data and module complexity
Q97. Test execution metric measures:
(A) Number of test cases executed versus planned
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Number of test cases executed versus planned
Q98. Metrics aid in process standardization by:
(A) Providing data to define best practices and benchmarks
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Providing data to define best practices and benchmarks
Q99. Software reliability growth metrics measure:
(A) Improvement in reliability as defects are fixed over time
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Improvement in reliability as defects are fixed over time
Q100. Ultimate goal of software metrics is:
(A) Improve quality, productivity, predictability, and process control
(B) Coding only
(C) UI only
(D) Hardware only
Answer: (A) Improve quality, productivity, predictability, and process control