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.

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 10 of 15

Explore more Topics under Software Engineering

01

Basics

02

Software Life Cycle Models

03

Requirements Modeling

04

Software Design Concepts

05

Software Components

06

Quality Management

07

Software Metrics

08

Software Testing

09

Software Management

10

Risk Management

11

Software Reliability

12

Advanced Software Engineering

13

People Management and Team Organization

14

Project Planning and Control

15

Requirements Engineering

16

Modeling

17

Software Architecture

18

Software Maintenance

19

Software Tools

Q91.

What are the five scale factors used in COCOMO 2?

Prencedentedness, development flexibility, architecture/risk resolution, team cohesion, process maturity

Novelty, conformance, risk elimination, stakeholder interactions, project organization maturity

Novelty, flexibility, risk resolution, team dynamics, maturity of project organization

Prencedentedness, flexibility, risk management, team dynamics, project maturity

Discuss

Answer: (a).Prencedentedness, development flexibility, architecture/risk resolution, team cohesion, process maturity Explanation:The five scale factors used in COCOMO 2 are Prencedentedness, development flexibility, architecture/risk resolution, team cohesion, and process maturity. These factors account for the novelty of the project, the need for conformance with pre-established and external interface requirements, the percentage of significant risks that have been eliminated, possible difficulties in stakeholder interactions, and the maturity of the project organization according to the Capability Maturity Model.

Q92.

How is reuse catered for in the original COCOMO model?

by adjusting the unadjusted value KLOC using a formula

by considering the fractions of the system that require redesign, recoding, and re-integration

by using a different set of cost drivers

by using a different exponent in the effort equation

Discuss

Answer: (b).by considering the fractions of the system that require redesign, recoding, and re-integration Explanation:In the original COCOMO model, reuse is catered for by separately considering the fractions of the system that require redesign, recoding, and re-integration. An adjustment factor AAF is then given by the formula AAF = 0.4DM + 0.3CM + 0.3IM. An adjusted value AKLOC, given by AKLOC = KLOC * AAF/100 is next used in the COCOMO formulae, instead of the unadjusted value KLOC. This way, a lower cost estimate is obtained if part of the system is reused.

Q93.

How is the exponent b in the COCOMO 2 effort equation determined?

by using a fixed value for all projects

by using a formula that takes into account five scale factors

by using the number of KSLOC or UFP as a base measure

by using the number of Object Points as a base measure

Discuss

Answer: (b).by using a formula that takes into account five scale factors Explanation:In COCOMO 2, the exponent b in the effort equation is determined by a formula that uses five scale factors. These scale factors are rated on a six-point scale and include factors such as unprecedentedness, development flexibility, architecture/risk resolution, team cohesion, and process maturity. The formula used to calculate the exponent b is b=1.01+0.01 * ΣWi.

Q94.

How is the effort needed to determine whether a component is appropriate for the present application represented in COCOMO 2?

as a fixed percentage

as a range from 0% to 8%

as a fixed number of lines of code

not represented

Discuss

Answer: (b).as a range from 0% to 8% Explanation:In COCOMO 2, the effort needed to determine whether a component is appropriate for the present application is represented as a range from 0% (no extra effort required) to 8% (extensive test, evaluation and documentation required), which is denoted by the degree of assessment and assimilation (AA).

Q95.

How is the equivalent number of new lines of code calculated in COCOMO 2?

by multiplying the number of lines of code by the adjustment factor AAF

by multiplying the number of lines of code by ( AAF+SU+AA )/100

by subtracting the number of reused lines of code from the total number of lines of code

not calculated

Discuss

Answer: (b).by multiplying the number of lines of code by ( AAF+SU+AA )/100 Explanation:In COCOMO 2, the equivalent number of new lines of code is calculated by multiplying the number of lines of code by (AAF+SU+AA)/100, where AAF is the adjustment factor, SU is the software understanding increment, and AA is the degree of assessment and assimilation.

Q96.

What are the factors that impact the cost of reuse in COCOMO 2?

The quality of the code being reused

The amount of effort needed to test the applicability of the component to be reused

The cost of developing reusable components

Both a and b

Discuss

Answer: (d).Both a and b Explanation:COCOMO 2 uses a more elaborate scheme to handle reuse effects. This scheme reflects two additional factors that impact the cost of reuse: the quality of the code being reused and the amount of effort needed to test the applicability of the component to be reused.

Q97.

What is the extra effort needed to reuse code if it is strongly modular, matches the application, and is well-documented?

10%

25%

50%

Discuss

Answer: (b).10% Explanation:If the software to be reused is strongly modular, strongly matches the application in which it is to be reused, and the code is well-organized and properly documented, then the extra effort needed to reuse this code is relatively low, and estimated to be 10%.

Q98.

What is the range of the degree of assessment and assimilation (AA) in COCOMO 2?

0% to 50%

10% to 20%

0% to 8%

20% to 30%

Discuss

Answer: (c).0% to 8% Explanation:The degree of assessment and assimilation (AA) in COCOMO 2 denotes the effort needed to determine whether a component is appropriate for the present application. It ranges from 0% (no extra effort required) to 8% (extensive test, evaluation and documentation required).

Q99.

How is the equivalent kilo number of new lines of code (EKLOC) calculated in COCOMO 2?

EKLOC=KLOC*(AAF+SU+AA)/100

EKLOC=KLOC*(AA+SU)/100

EKLOC=KLOC*(AAF+AA)/100

EKLOC=KLOC*(AAF*SU*AA)/100

Discuss

Answer: (a).EKLOC=KLOC*(AAF+SU+AA)/100 Explanation:The equivalent kilo number of new lines of code, EKLOC is calculated by multiplying the number of lines of code (KLOC) with the adjustment factor AAF, the software understanding increment SU, and the degree of assessment and assimilation (AA) and dividing by 100.

Q100.

What is one of the main problems in applying cost estimation models?

Lack of data about past projects

Lack of expertise in the estimators

Political arguments entering the arena

Difficulty in collecting data

Discuss

Answer: (a).Lack of data about past projects Explanation:One of the main problems in applying these models is the sheer lack of quantitative data about past projects.

Page 10 of 15

Welcome to the Cost Estimation MCQs Page

Cost Estimation MCQs | Page 10 of 15

Explore more Topics under Software Engineering

Basics

Software Life Cycle Models

Requirements Modeling

Software Design Concepts

Software Components

Quality Management

Software Metrics

Software Testing

Software Management

Risk Management

Software Reliability

Advanced Software Engineering

People Management and Team Organization

Project Planning and Control

Requirements Engineering

Modeling

Software Architecture

Software Maintenance

Software Tools

Suggested Topics

MySQL Database

Web Technologies

MS Office

HTML

Object Oriented Programming Using C++

Discrete Mathematics

C Programming

MongoDB

IT Fundamentals