Software Project Estimation Questions and Answers

Q: Boehm suggests an approach that addresses project objectives, milestones and schedules, responsibilities, management and technical approaches and required resources. This principle is called as ______.

The principle is the W5HH principle.Barry Boehm's W5HH principle organises a project plan around seven questions: Why is the system being developed? What will be done? When will it be done? Who is responsible? Where are they located? How will the job be done technically and managerially? How much of each resource is needed? These cover objectives, milestones and schedules, responsibilities, approaches and resources.'W3HH' and 'WHO' are not the names of Boehm's principle.

Q: Which estimating technique uses historical data from similar projects ?

The technique is analogous estimation.Analogous (top-down) estimation bases the effort, cost or duration of a new project on actual figures from similar past projects, adjusted for known differences. It is quick and useful early on, when detail is scarce.The Delphi technique pools expert opinion through anonymous rounds until a consensus forms. COCOMO is a parametric model that computes effort from size (KLOC) and cost drivers. Its constants were fitted to historical data, but it is a formula, not a comparison with similar projects. Function point analysis measures software size from its functions.

Q: Consider a software project with the following information domain characteristics for calculation of function point metricNumber of external inputs (I) = 30Number of external outputs (O) = 60Number of external inquiries (E) = 23Number of files (F) = 08Number of external interfaces (N) = 02It is given that the complexity weighting factors for I, O, E, F and N are 4, 5, 4, 10 and 7, respectively. It is also given that, out of fourteen value adjustment factors that influence the development effort, four factors are not applicable, each of the other four factors have value 3, and each of the remaining factors have value 4. The computed value of function point metric is

The function point value is 612.06.Unadjusted function points, then the value adjustment, with 4 factors at 0, 4 at 3 and the other 6 at 4:\[ \begin{aligned} UFP &= 30(4) + 60(5) + 23(4) + 8(10) + 2(7) \\ &= 120 + 300 + 92 + 80 + 14 = 606 \\ \sum F &= 4(3) + 6(4) = 36 \\ VAF &= 0.65 + 0.01 \times 36 = 1.01 \\ FP &= 606 \times 1.01 = 612.06 \end{aligned} \]606 is the unadjusted count, 1.01 the adjustment factor and 0.65 its constant, so none of them is the function point value.

Q: In project management, the 'Critical Path' refers to

The critical path is the sequence of tasks that determines the project's finish date.In network scheduling (CPM or PERT), the critical path is the longest chain of dependent activities from start to finish. Its activities have zero float, so any delay on them delays the whole project, and the length of this path is the project duration.The path's length gives the minimum project duration, but it is defined as the longest chain of tasks, not as the shortest time, which is why option A is the trap. It has nothing to do with the likelihood of failure or with budgets.

Q: According to a statistical report : "over 30% of all software projects are cancelled before completion and over 70% of the remainder fail to deliver expected features". What must be the reason for such a situation ?

The key's answer is Poor requirements management.Surveys of failed projects, such as the Standish Group reports behind figures like these, put incomplete, unclear and changing requirements at the top of the causes of cancellation and of systems that do not do what users expected. A project built on badly managed requirements delivers the wrong features however well it is coded and tested.Change management and quality control matter, but they act on a system whose requirements are already set; the question bank this comes from treats requirements as the root cause, not all three equally.

11.

Boehm suggests an approach that addresses project objectives, milestones and schedules, responsibilities, management and technical approaches and required resources. This principle is called as ______.

A.W3HH principle
B.WHO principle
C.W5HH principle
D.None of the above

Exam Year(s)

Tripura Public Service Commission - 2019,

Answer: C

The principle is the W5HH principle.

Barry Boehm's W5HH principle organises a project plan around seven questions: Why is the system being developed? What will be done? When will it be done? Who is responsible? Where are they located? How will the job be done technically and managerially? How much of each resource is needed? These cover objectives, milestones and schedules, responsibilities, approaches and resources.

'W3HH' and 'WHO' are not the names of Boehm's principle.

Discuss in Forum

12.

Which estimating technique uses historical data from similar projects ?

A.Delphi technique
B.COCOMO model
C.Function point analysis
D.Analogous estimation

Exam Year(s)

Tripura Public Service Commission - 2026,

Answer: D

The technique is analogous estimation.

Analogous (top-down) estimation bases the effort, cost or duration of a new project on actual figures from similar past projects, adjusted for known differences. It is quick and useful early on, when detail is scarce.

The Delphi technique pools expert opinion through anonymous rounds until a consensus forms. COCOMO is a parametric model that computes effort from size (KLOC) and cost drivers. Its constants were fitted to historical data, but it is a formula, not a comparison with similar projects. Function point analysis measures software size from its functions.

Discuss in Forum

13.

Consider a software project with the following information domain characteristics for calculation of function point metric

Number of external inputs (I) = 30
Number of external outputs (O) = 60
Number of external inquiries (E) = 23
Number of files (F) = 08
Number of external interfaces (N) = 02

It is given that the complexity weighting factors for I, O, E, F and N are 4, 5, 4, 10 and 7, respectively. It is also given that, out of fourteen value adjustment factors that influence the development effort, four factors are not applicable, each of the other four factors have value 3, and each of the remaining factors have value 4. The computed value of function point metric is

A.612.06
B.1.01
C.606
D.0.65

Exam Year(s)

Tripura Public Service Commission - 2025,

Answer: A

The function point value is 612.06.

Unadjusted function points, then the value adjustment, with 4 factors at 0, 4 at 3 and the other 6 at 4:

\[ \begin{aligned} UFP &= 30(4) + 60(5) + 23(4) + 8(10) + 2(7) \\ &= 120 + 300 + 92 + 80 + 14 = 606 \\ \sum F &= 4(3) + 6(4) = 36 \\ VAF &= 0.65 + 0.01 \times 36 = 1.01 \\ FP &= 606 \times 1.01 = 612.06 \end{aligned} \]

606 is the unadjusted count, 1.01 the adjustment factor and 0.65 its constant, so none of them is the function point value.

Discuss in Forum

14.

In project management, the 'Critical Path' refers to

A.The shortest possible time to complete the project
B.The sequence of tasks that determines the project's finish date
C.The task that are more likely to fail
D.The list of tasks that have the low budget

Exam Year(s)

Tripura Public Service Commission - 2026,

Answer: B

The critical path is the sequence of tasks that determines the project's finish date.

In network scheduling (CPM or PERT), the critical path is the longest chain of dependent activities from start to finish. Its activities have zero float, so any delay on them delays the whole project, and the length of this path is the project duration.

The path's length gives the minimum project duration, but it is defined as the longest chain of tasks, not as the shortest time, which is why option A is the trap. It has nothing to do with the likelihood of failure or with budgets.

Discuss in Forum

15.

According to a statistical report : "over 30% of all software projects are cancelled before completion and over 70% of the remainder fail to deliver expected features". What must be the reason for such a situation ?

A.Poor change management
B.Poor requirements management
C.Poor quality control
D.All of the above

Exam Year(s)

Tripura Public Service Commission - 2019,

Answer: B

The key's answer is Poor requirements management.

Surveys of failed projects, such as the Standish Group reports behind figures like these, put incomplete, unclear and changing requirements at the top of the causes of cancellation and of systems that do not do what users expected. A project built on badly managed requirements delivers the wrong features however well it is coded and tested.

Change management and quality control matter, but they act on a system whose requirements are already set; the question bank this comes from treats requirements as the root cause, not all three equally.

Discuss in Forum

16.

Which of the following metric does not depend on the programming language used ?

A.Line of code
B.Function count
C.Member of token
D.All of the above

Exam Year(s)

UGC NET - 2012,

Answer: B

The metric that does not depend on the programming language is the function count.

Function points are worked out from the functions the system delivers to the user, such as inputs, outputs, inquiries and files, so the result is the same whatever language the program is written in. Lines of code (A) and the number of tokens (C) depend directly on the language, because one statement in one language can take many lines in another. Hence (D) is wrong.

Discuss in Forum

17.

Function points can be calculated by

A.UFP ∗ CAF
B.UFP ∗ FAC
C.UFP ∗ Cost
D.UFP ∗ Productivity

Exam Year(s)

UGC NET - 2013,

Answer: A

Function points are calculated as the unadjusted function point count multiplied by the complexity adjustment factor, \(FP = UFP \times CAF\). The UFP is the weighted count of inputs, outputs, inquiries, files and interfaces, and the CAF adjusts it for fourteen general system characteristics.

The other products are not part of the method: "FAC" is not the adjustment factor, and multiplying UFP by cost or by productivity would give a monetary or effort-related figure rather than a function point count.

Discuss in Forum

18.

COCOMO stands for

A.COmposite COst MOdel
B.COnstructive COst MOdel
C.COnstructive COmposite MOdel
D.COmprehensive COnstruction MOdel

Exam Year(s)

UGC NET - 2013,

Answer: B

COCOMO stands for COnstructive COst MOdel, the software cost estimation model proposed by Barry Boehm in 1981. It predicts effort in person-months, and from it development time and staffing, from the estimated size of the product in thousands of delivered source instructions, with the multipliers depending on whether the project is organic, semi-detached or embedded. The other three expansions, Composite Cost Model, Constructive Composite Model and Comprehensive Construction Model, are invented names that do not belong to any estimation technique, so only (B) is right.

Discuss in Forum

19.

While estimating the cost of software, Lines Of Code (LOC) and Function Points (FP) are used to measure which one of the following ?

A.Length of code
B.Size of software
C.Functionality of software
D.None of the above

Exam Year(s)

UGC NET - 2013,

Answer: B

Lines of code and function points are both measures of the size of a software product, so the answer is (B). LOC counts the physical or logical source lines, and FP counts the functionality delivered to the user in terms of inputs, outputs, inquiries, files and interfaces, adjusted for complexity. Both feed estimation models such as COCOMO or FP-based productivity figures to give effort and cost. Length of code is only what LOC itself counts, and functionality is what FP counts, so each of those names just one of the two measures. Since neither alone covers both, (A) and (C) fall short, and (D) is wrong because size is a correct answer.

Discuss in Forum

20.

Match the following :

a. Watson-Felix model	i. Failure intensity
b. Quick-Fix model	ii. Cost estimation
c. Putnam resource allocation model	iii. Project planning
d. Logarithmic-Poisson Model	iv. Maintenance

Codes : a b c d

A.ii i iv iii
B.i ii iv iii
C.ii i iii iv
D.ii iv iii i

Exam Year(s)

UGC NET - 2013,

Answer: D

The correct matching is the Watson-Felix (Walston-Felix) model with cost estimation (ii), the Quick-Fix model with maintenance (iv), the Putnam resource allocation model with project planning (iii), and the Logarithmic-Poisson model with failure intensity (i). This is code ii iv iii i, option (D).

Options (B) and (C) disagree on the first pair or the second pair: the Quick-Fix model is a maintenance model and not a cost estimation or a failure intensity model, and the Watson-Felix model estimates cost, not failure intensity. Option (A) agrees on the first pair but gives the Quick-Fix model the failure intensity.

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