Software Project Estimation Questions and Answers

Q: The formula for estimating the development effort and development time of an embedded product is :

The formula is Effort = 3.6 \((\text{KLOC})^{1.20}\) PM, Tdev = 2.5\((\text{Effort})^{0.32}\) Months.In Boehm's basic COCOMO, effort is \(a(\text{KLOC})^{b}\) person-months and development time is \(c(\text{Effort})^{d}\) months, with constants depending on the project class:ClassabcdOrganic2.41.052.50.38Semi-detached3.01.122.50.35Embedded3.61.202.50.32Option (A) is the organic formula and (B) the semi-detached one. Option (D) mixes organic effort with the semi-detached time exponent.

Q: Vocabulary of a program is defined as :

The vocabulary is \(n = n_1 + n_2\).In Halstead's software science, \(n_1\) is the number of distinct operators and \(n_2\) the number of distinct operands in a program. The vocabulary is the total number of distinct tokens, their sum.The related measures are program length \(N = N_1 + N_2\), the total count of operator and operand occurrences, and volume \(V = N \log_2 n\). Differences, products and ratios of \(n_1\) and \(n_2\) are not Halstead measures, so the other options are wrong.

Q: Which model assumes that effort and development time are functions of product size alone ?

The model is Basic COCOMO.Boehm's Basic COCOMO estimates effort and development time from product size alone:\[ E = a\,(KLOC)^{b}, \quad D = c\,E^{d} \]with constants depending only on whether the project is organic, semi-detached or embedded.Intermediate COCOMO multiplies the estimate by an effort adjustment factor from 15 cost drivers (product, hardware, personnel and project attributes), and Detailed COCOMO applies those drivers phase by phase, so neither depends on size alone. 'COCOMO' on its own names the whole family.

Q: One of the following is most desirable when using LOC as a size oriented metric ?

The desirable feature is that LOC can be easily computed.Lines of code is popular as a size metric chiefly because it is simple: once code exists, counting its lines is easy and can be automated, and a large body of historical data uses it.The other options are drawbacks or false. LOC is language dependent, which is a disadvantage, since the same function takes different numbers of lines in different languages; so 'language independent' is untrue. And LOC cannot be measured before design, because the code does not yet exist; it can only be estimated, which is one reason function points were introduced.

Q: Which of the following is not a size metric ?

The one that is not a size metric is Cyclomatic Complexity.Cyclomatic complexity (McCabe) measures the logical complexity of a program: the number of linearly independent paths through its control-flow graph, V(G) = E - N + 2. Two programs of the same size can have very different cyclomatic complexity.The others measure size. Lines of code count program lines. Function count (function points) measures size from the functionality delivered. Program length is Halstead's size measure, the total number of operator and operand occurrences, N = N1 + N2.

Q: In COCOMO II model PREX stands for ................. .

PREX stands for personnel experience.PREX is one of the effort multipliers of the COCOMO II early design model. It combines the team's application experience, platform experience and language and tool experience into one rating.Reliability and complexity is RCPX, personnel capability is PERS, and 'personal exchange' is not a COCOMO II attribute.

Q: The first version of the COCOMO model (COCOMO 81) was a .............. level model where the levels corresponded to the detail of the analysis of the cost estimate.

COCOMO 81 was a three-level model.Barry Boehm's original COCOMO (1981) had three levels of increasing detail: basic COCOMO, a quick estimate from size alone; intermediate COCOMO, which adds cost drivers for product, hardware, personnel and project attributes; and detailed COCOMO, which applies the drivers phase by phase.COCOMO II later replaced these with differently named sub-models, but the 1981 model had exactly three levels, not one, two or four.

Q: What is the full form of the "COCOMO" model ?

COCOMO stands for Constructive Cost Model.COCOMO is the software cost estimation model published by Barry Boehm in 1981. It estimates effort in person-months, and from that development time, chiefly from the estimated size of the program in thousands of lines of code (KLOC). It comes in basic, intermediate and detailed forms, and was revised as COCOMO II.'Cost Constructive Model' reverses the words, and 'Constructive Case Model' replaces Cost with Case. The order is Constructive, then Cost: CO-CO-MO.

Which of the following software is used by a wide range of industries for project planning, resource allocation and scheduling?

A.CRM software
B.Project management software
C.Word processor
D.Firewall software

Exam Year(s)

DSSSB TGT - 2023,

Answer: B

Project management software is used across industries for project planning, resource allocation and scheduling. CRM software manages customer relationships, a word processor prepares documents and a firewall program protects a network from unauthorised access, so none of these does the planning and scheduling named in the question. Examples of such software are Microsoft Project and Primavera, which use charts and timelines to schedule tasks and resources.

Discuss in Forum

Which of the following projects deals with developing a well understood application program, the size of the development team is reasonably small, and the team members are experienced in developing similar types of projects?

A.Flexible
B.Semidetached
C.Organic
D.Embedded

Exam Year(s)

DSSSB TGT - 2023,

Answer: C

An organic project is the type in which the application is well understood, the team is small and the team members have experience of similar projects. In the COCOMO classification, a semidetached project is of intermediate size and experience, and an embedded project is one with strict hardware and operational constraints. 'Flexible' is not one of the three COCOMO project types, so organic is the answer. The three COCOMO project classes are organic, semidetached and embedded, in increasing order of constraint and complexity.

Discuss in Forum

The formula for estimating the development effort and development time of an embedded product is :

A.Effort = 2.4 \((\text{KLOC})^{1.05}\) PM, Tdev = 2.5\((\text{Effort})^{0.38}\) Months
B.Effort = 3.0 \((\text{KLOC})^{1.12}\) PM, Tdev = 2.5\((\text{Effort})^{0.35}\) Months
C.Effort = 3.6 \((\text{KLOC})^{1.20}\) PM, Tdev = 2.5\((\text{Effort})^{0.32}\) Months
D.Effort = 2.4 \((\text{KLOC})^{1.05}\) PM, Tdev = 2.5\((\text{Effort})^{0.35}\) Months

Exam Year(s)

MH SET - 2019, SET Exam - 2019,

Answer: C

The formula is Effort = 3.6 \((\text{KLOC})^{1.20}\) PM, Tdev = 2.5\((\text{Effort})^{0.32}\) Months.

In Boehm's basic COCOMO, effort is \(a(\text{KLOC})^{b}\) person-months and development time is \(c(\text{Effort})^{d}\) months, with constants depending on the project class:

Class	a	b	c	d
Organic	2.4	1.05	2.5	0.38
Semi-detached	3.0	1.12	2.5	0.35
Embedded	3.6	1.20	2.5	0.32

Option (A) is the organic formula and (B) the semi-detached one. Option (D) mixes organic effort with the semi-detached time exponent.

Discuss in Forum

Vocabulary of a program is defined as :

A.\(n = n_{1} + n_{2}\)
B.\(n = n_{1} - n_{2}\)
C.\(n = n_{1} \times n_{2}\)
D.\(n = n_{1} / n_{2}\)

Exam Year(s)

MH SET - 2021, SET Exam - 2021,

Answer: A

The vocabulary is \(n = n_1 + n_2\).

In Halstead's software science, \(n_1\) is the number of distinct operators and \(n_2\) the number of distinct operands in a program. The vocabulary is the total number of distinct tokens, their sum.

The related measures are program length \(N = N_1 + N_2\), the total count of operator and operand occurrences, and volume \(V = N \log_2 n\). Differences, products and ratios of \(n_1\) and \(n_2\) are not Halstead measures, so the other options are wrong.

Discuss in Forum

Which model assumes that effort and development time are functions of product size alone ?

A.Basic COCOMO
B.Detailed COCOMO
C.Intermediate COCOMO
D.COCOMO

Exam Year(s)

MH SET - 2021, SET Exam - 2021,

Answer: A

The model is Basic COCOMO.

Boehm's Basic COCOMO estimates effort and development time from product size alone:

\[ E = a\,(KLOC)^{b}, \quad D = c\,E^{d} \]

with constants depending only on whether the project is organic, semi-detached or embedded.

Intermediate COCOMO multiplies the estimate by an effort adjustment factor from 15 cost drivers (product, hardware, personnel and project attributes), and Detailed COCOMO applies those drivers phase by phase, so neither depends on size alone. 'COCOMO' on its own names the whole family.

Discuss in Forum

One of the following is most desirable when using LOC as a size oriented metric ?

A.LOC is language dependent
B.LOC is language independent
C.LOC can be computed before design phase
D.LOC can be easily computed

Exam Year(s)

MH SET - 2023, SET Exam - 2023,

Answer: D

The desirable feature is that LOC can be easily computed.

Lines of code is popular as a size metric chiefly because it is simple: once code exists, counting its lines is easy and can be automated, and a large body of historical data uses it.

The other options are drawbacks or false. LOC is language dependent, which is a disadvantage, since the same function takes different numbers of lines in different languages; so 'language independent' is untrue. And LOC cannot be measured before design, because the code does not yet exist; it can only be estimated, which is one reason function points were introduced.

Discuss in Forum

Which of the following is not a size metric ?

A.LOC
B.Function Count
C.Program Length
D.Cyclomatic Complexity

Exam Year(s)

MH SET - 2023, SET Exam - 2023,

Answer: D

The one that is not a size metric is Cyclomatic Complexity.

Cyclomatic complexity (McCabe) measures the logical complexity of a program: the number of linearly independent paths through its control-flow graph, V(G) = E - N + 2. Two programs of the same size can have very different cyclomatic complexity.

The others measure size. Lines of code count program lines. Function count (function points) measures size from the functionality delivered. Program length is Halstead's size measure, the total number of operator and operand occurrences, N = N1 + N2.

Discuss in Forum

In COCOMO II model PREX stands for ................. .

A.Personnel experience
B.Reliability and complexity
C.Personnel capability
D.Personal exchange

Exam Year(s)

MH SET - 2024, SET Exam - 2024,

Answer: A

PREX stands for personnel experience.

PREX is one of the effort multipliers of the COCOMO II early design model. It combines the team's application experience, platform experience and language and tool experience into one rating.

Reliability and complexity is RCPX, personnel capability is PERS, and 'personal exchange' is not a COCOMO II attribute.

Discuss in Forum

The first version of the COCOMO model (COCOMO 81) was a .............. level model where the levels corresponded to the detail of the analysis of the cost estimate.

A.one
B.two
C.three
D.four

Exam Year(s)

MH SET - 2025, SET Exam - 2025,

Answer: C

COCOMO 81 was a three-level model.

Barry Boehm's original COCOMO (1981) had three levels of increasing detail: basic COCOMO, a quick estimate from size alone; intermediate COCOMO, which adds cost drivers for product, hardware, personnel and project attributes; and detailed COCOMO, which applies the drivers phase by phase.

COCOMO II later replaced these with differently named sub-models, but the 1981 model had exactly three levels, not one, two or four.

Discuss in Forum

10.

What is the full form of the "COCOMO" model ?

A.Cost Constructive Model
B.Constructive Cost Model
C.Constructive Case Model
D.None of the above

Exam Year(s)

Tripura Public Service Commission - 2026,

Answer: B

COCOMO stands for Constructive Cost Model.

COCOMO is the software cost estimation model published by Barry Boehm in 1981. It estimates effort in person-months, and from that development time, chiefly from the estimated size of the program in thousands of lines of code (KLOC). It comes in basic, intermediate and detailed forms, and was revised as COCOMO II.

'Cost Constructive Model' reverses the words, and 'Constructive Case Model' replaces Cost with Case. The order is Constructive, then Cost: CO-CO-MO.

Discuss in Forum

Loading…

Topics

Other Subjects

Tags: Software Project Estimation Questions and Answers || Software Project Estimation MCQ Questions and Answers || Software Project Estimation GK Questions and Answers || Software Project Estimation GK MCQ Questions || Software Project Estimation Multiple Choice Questions and Answers || Software Project Estimation GK || GK on Software Project Estimation || Software Engineering Questions and Answers || Software Engineering MCQ Questions and Answers || Software Engineering GK Questions and Answers || GK on Software Engineering

Software Project Estimation Questions and Answers

Topics

Other Subjects

About Us

Stay informed about all important Dates & Notifications