adplus-dvertising

Welcome to the Cost Estimation MCQs Page

Dive deep into the fascinating world of Cost Estimation with our comprehensive set of Multiple-Choice Questions (MCQs). This page is dedicated to exploring the fundamental concepts and intricacies of Cost Estimation, a crucial aspect of Software Engineering. In this section, you will encounter a diverse range of MCQs that cover various aspects of Cost Estimation, from the basic principles to advanced topics. Each question is thoughtfully crafted to challenge your knowledge and deepen your understanding of this critical subcategory within Software Engineering.

frame-decoration

Check out the MCQs below to embark on an enriching journey through Cost Estimation. Test your knowledge, expand your horizons, and solidify your grasp on this vital area of Software Engineering.

Note: Each MCQ comes with multiple answer choices. Select the most appropriate option and test your understanding of Cost Estimation. You can click on an option to test your knowledge before viewing the solution for a MCQ. Happy learning!

Cost Estimation MCQs | Page 9 of 15

Discuss
Answer: (b).By counting the number of inputs, outputs, inquiries, etc. Explanation:The Early Design model uses unadjusted function points (UFPs) as its basic size measure, which are counted in the same way as in FPA by counting the number of inputs, outputs, inquiries, etc.
Discuss
Answer: (a).The Application Composition model counts Object Points while the Early Design model counts Function Points Explanation:The Application Composition model is based on counting the number of screens, reports, and 3GL components in the application while the Early Design model uses unadjusted function points as its basic size measure.
Discuss
Answer: (a).Object Points are easier to determine than Function Points Explanation:The Application Composition model is based on counting Object Points which are considered to be easier to determine and at an earlier point in time than Function Points.
Discuss
Answer: (d).All of the above Explanation:The total effort in the Application Composition model is estimated by counting the number of screens, reports and 3GL components in the application, determining the complexity level of each screen, report and 3GL component, using numbers from a classification table to determine relative effort, and summing the Object Points for the individual objects.
Discuss
Answer: (d).All of the above Explanation:The Post-Architecture model differs from the original COCOMO model in its set of cost drivers, the use of lines of code as its base measure, and the range of values of the exponent b.
Discuss
Answer: (a).Four new cost drivers have been introduced, two have been dropped, and the productivity influence of some cost drivers has been increased or decreased Explanation:Four new cost drivers have been introduced, two have been dropped, and the productivity influence of some cost drivers has been increased or decreased in COCOMO 2.
Q87.
What is the formula used to determine the exponent b in the COCOMO 2 effort equation?
Discuss
Answer: (b).b = 1.01 + 0.01 * ΣWi Explanation:The exponent b for the effort equation in COCOMO 2 is determined by the formula: b = 1.01 + 0.01 * ΣWi where Wi are the five scale factors rated on a six-point scale from very low (5) to extra high (0).
Q88.
Can both KSLOC and UFP be used as a base measure in COCOMO 2?
Discuss
Answer: (a).Yes Explanation:In COCOMO 2, the user may use both KSLOC and UFP as a base measure. It is also possible to use UFP for part of the system and then convert the counts to KSLOC counts before applying the effort equation.
Discuss
Answer: (d).All of the above Explanation:In the Application Composition model of COCOMO 2, the total effort is estimated by counting the number of screens, reports, and 3GL components in the application, determining the complexity level of each screen and report, using numbers given in a classification table similar to those in FPA, and summing the Object Points for the individual objects.
Discuss
Answer: (a).By separately considering the fractions of the system that require redesign, recoding, and re-integration Explanation:In COCOMO 2, reuse is handled by separately considering the fractions of the system that require redesign, recoding, and re-integration, and using an adjustment factor (AAF) to lower the cost estimate if part of the system is reused.

Suggested Topics

Are you eager to expand your knowledge beyond Software Engineering? We've curated a selection of related categories that you might find intriguing.

Click on the categories below to discover a wealth of MCQs and enrich your understanding of Computer Science. Happy exploring!