COMPUTER SCIENCE - PAGE 13
1. How does a software project manager nned to act to minimize the risk of software failure?
1. Request a large budget
2. Start on the right foot
3. Track progress
4. Both 2 and 3
Ans: 4
2. Which of these are reasons for using technical product measures during software development?
1. Large body of scientific evidence supports their use
2. Provides software engineers with an objective mechanism for assessing software quality
3. They allow all software quality information to be expressed unambiguously as a single number
4. All of the above
Ans: 2
3. One of the most important attributes for a software product metric is that it should be
1. Easy to compute
2. Qualitative in nature
3. Reliable over time
4. Widely applicable
Ans: 1
4. The specification metrics proposed by Davis address which two characteristics of the software requirements?
1. Functionality and performance
2. Performance and completeness
3. Specificity and completeness
4. Specificity and functionality
Ans: 3
5. Which of the following is not a measurable characteristic of an object-oriented design?
1. Completeness
2. Efficiency
3. Size
4. Volatility
Ans: 2
6. The depth of inheritance tree (DIT) metric can give an OO software designer a reading on the
1. Attributes required for each class
2. Completion time required for system implementation
3. Complexity of the class hierarchy
4. Level of object reusability achieved
Ans: 2
7. If you encounter a class with a large responsibility (large class size or CS value) you should consider
1. Making it a base class
2. Making it a sub class
3. Partitioning the class
4. Starting a new class hierarchy
Ans: 3
8. Software testing metrics fall into two broad categories
1. Metrics that focus on test coverage
2. Metrics that estimate the duration of the testing process
3. Metrics that predict thenumber of test cases required
4. Both 2 and 3
Ans: 4
9. The IEEE software maturity index is used to provide a measure of the
1. Maintainability of a software product based on its availability
2. Relative age of a software product being considered for retirement
3. Reliability of a software product following regression testing
4. Stability of a software product as it is modified during maintenance
Ans: 4
10. Which of these are valid reaons for measuring software processes, products and resources
1. To characterize them
2. To evaluate them
3. To improve them
4. All of the above
Ans: 4
11. Which of the following items are not measured by software project metrics?
1. Inputs
2. Markets
3. Outputs
4. Results
Ans: 2
12. Which of the following software quality factors is most likely to be affected by radical changes to computing architectures?
1. Operation
2. Transition
3. Revision
4. None of the above
Ans: 4
13. Which of the following provide useful measures of software quality?
1. Correctness, business relevance, integrity, usuability
2. Reliability, maintainability, integrity, sales
3. Correctness, maintainability, size, satisfaction
4. Correctness, maintainability, integrity, usuability
Ans: 4
14. Why is it important to measure the process of software engineering and software it produces?
1. It is really not necessary unless the project is extremely complex
2. To determine costs and allow a profit margin to be set
3. To determine whether a software group is improving or not
4. To make software engineering more like other engineering processes
Ans: 3
15. The objective of software project planning is to
1. Convince the customer that a project is feasible
2. Make use of historical project data
3. Enable a manager tomake reasonable estimates of cost and schedule
4. Determine the probable profit margin prior to bidding on a project
Ans: 3
16. Reusable software components must be
1. Catalogued for easy reference
2. Standardized for easy application
3. Validated for easy integration
4. All of the above
Ans: 4
17. Software project estimation techniques can be broadly classified under which of the following headings?
1. Automated processes
2. Decomposition techniques
3. Empirical models
4. Both 2 and 3
Ans: 4
18. LOC-based estimation techniques require problem decomposition based on
1. Informationdomain values
2. Project schedule
3. Software functions
4. Process activities
Ans: 3
19. FP-based estimation techniques require problem decomposition based on
1. Information domain values
2. Project schedule
3. Software functions
4. Process activities
Ans: 1
20. Empirical estimation models are typically based on
1. Expert judgement based on past project experiences
2. Refinement of expected value estimation
3. Regression models derived from historical project data
4. Trial and error determination of the parameteres and coefficients
Ans: 3
21. COCOMO II is an example of a suite of modern empirical estimation models that require sizing information expressed as:
1. Function points
2. Lines of code
3. Object points
4. All of the above
Ans: 4
22. In agile software development estimation techniques focus on the time required to complete each
1. Increment
2. Function
3. Task
4. All of the above
Ans: 1
23. Which of the following is not one of the guiding principles of software project scheduling
1. Compartmentalization
2. Market assessment
3. Time allocation
4. Effort validation
Ans: 2
24. The software equation can be used to show that by extending the project deadline slightly
1. Fewer people are required
2. You are guaranteed to meet the deadline
3. More lines of code can be produced
4. None of the above
Ans: 1
25. For purposes of determining the major engineering tasks and distributing them on the project time line, the project manager should assume that the process model used is
1. Linear
2. Sequential
3. Iterative evolutionary
4. All of the above
Ans: 4
1. Request a large budget
2. Start on the right foot
3. Track progress
4. Both 2 and 3
Ans: 4
2. Which of these are reasons for using technical product measures during software development?
1. Large body of scientific evidence supports their use
2. Provides software engineers with an objective mechanism for assessing software quality
3. They allow all software quality information to be expressed unambiguously as a single number
4. All of the above
Ans: 2
3. One of the most important attributes for a software product metric is that it should be
1. Easy to compute
2. Qualitative in nature
3. Reliable over time
4. Widely applicable
Ans: 1
4. The specification metrics proposed by Davis address which two characteristics of the software requirements?
1. Functionality and performance
2. Performance and completeness
3. Specificity and completeness
4. Specificity and functionality
Ans: 3
5. Which of the following is not a measurable characteristic of an object-oriented design?
1. Completeness
2. Efficiency
3. Size
4. Volatility
Ans: 2
6. The depth of inheritance tree (DIT) metric can give an OO software designer a reading on the
1. Attributes required for each class
2. Completion time required for system implementation
3. Complexity of the class hierarchy
4. Level of object reusability achieved
Ans: 2
7. If you encounter a class with a large responsibility (large class size or CS value) you should consider
1. Making it a base class
2. Making it a sub class
3. Partitioning the class
4. Starting a new class hierarchy
Ans: 3
8. Software testing metrics fall into two broad categories
1. Metrics that focus on test coverage
2. Metrics that estimate the duration of the testing process
3. Metrics that predict thenumber of test cases required
4. Both 2 and 3
Ans: 4
9. The IEEE software maturity index is used to provide a measure of the
1. Maintainability of a software product based on its availability
2. Relative age of a software product being considered for retirement
3. Reliability of a software product following regression testing
4. Stability of a software product as it is modified during maintenance
Ans: 4
10. Which of these are valid reaons for measuring software processes, products and resources
1. To characterize them
2. To evaluate them
3. To improve them
4. All of the above
Ans: 4
11. Which of the following items are not measured by software project metrics?
1. Inputs
2. Markets
3. Outputs
4. Results
Ans: 2
12. Which of the following software quality factors is most likely to be affected by radical changes to computing architectures?
1. Operation
2. Transition
3. Revision
4. None of the above
Ans: 4
13. Which of the following provide useful measures of software quality?
1. Correctness, business relevance, integrity, usuability
2. Reliability, maintainability, integrity, sales
3. Correctness, maintainability, size, satisfaction
4. Correctness, maintainability, integrity, usuability
Ans: 4
14. Why is it important to measure the process of software engineering and software it produces?
1. It is really not necessary unless the project is extremely complex
2. To determine costs and allow a profit margin to be set
3. To determine whether a software group is improving or not
4. To make software engineering more like other engineering processes
Ans: 3
15. The objective of software project planning is to
1. Convince the customer that a project is feasible
2. Make use of historical project data
3. Enable a manager tomake reasonable estimates of cost and schedule
4. Determine the probable profit margin prior to bidding on a project
Ans: 3
16. Reusable software components must be
1. Catalogued for easy reference
2. Standardized for easy application
3. Validated for easy integration
4. All of the above
Ans: 4
17. Software project estimation techniques can be broadly classified under which of the following headings?
1. Automated processes
2. Decomposition techniques
3. Empirical models
4. Both 2 and 3
Ans: 4
18. LOC-based estimation techniques require problem decomposition based on
1. Informationdomain values
2. Project schedule
3. Software functions
4. Process activities
Ans: 3
19. FP-based estimation techniques require problem decomposition based on
1. Information domain values
2. Project schedule
3. Software functions
4. Process activities
Ans: 1
20. Empirical estimation models are typically based on
1. Expert judgement based on past project experiences
2. Refinement of expected value estimation
3. Regression models derived from historical project data
4. Trial and error determination of the parameteres and coefficients
Ans: 3
21. COCOMO II is an example of a suite of modern empirical estimation models that require sizing information expressed as:
1. Function points
2. Lines of code
3. Object points
4. All of the above
Ans: 4
22. In agile software development estimation techniques focus on the time required to complete each
1. Increment
2. Function
3. Task
4. All of the above
Ans: 1
23. Which of the following is not one of the guiding principles of software project scheduling
1. Compartmentalization
2. Market assessment
3. Time allocation
4. Effort validation
Ans: 2
24. The software equation can be used to show that by extending the project deadline slightly
1. Fewer people are required
2. You are guaranteed to meet the deadline
3. More lines of code can be produced
4. None of the above
Ans: 1
25. For purposes of determining the major engineering tasks and distributing them on the project time line, the project manager should assume that the process model used is
1. Linear
2. Sequential
3. Iterative evolutionary
4. All of the above
Ans: 4
- Computer Application
- Computer Application- Page 1
- Computer Science
- Computer Science- Page 1
- Computer Science- Page 2
- Computer Science- Page 3
- Computer Science- Page 4
- Computer Science- Page 5
- Computer Science- Page 6
- Computer Science- Page 7
- Computer Science- Page 8
- Computer Science- Page 9
- Computer Science- Page 10
- Computer Science- Page 11
- Computer Science- Page 12
- Computer Science- Page 13
- Computer Science- Page 14
- Computer Science- Page 15