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

Q131.
What is the impact of an inexperienced software cost estimator on a project's estimated effort?
Discuss
Answer: (b).It increases the estimated effort Explanation:Studies in other fields show that inexperienced people tend to overestimate their abilities and performance. It is suggested that the same is true for people estimating software cost, leading to cost and schedule overruns.
Discuss
Answer: (a).A consistent estimate across different models Explanation:The values T computed by cost estimation models represent nominal development times and the various models show a remarkable consistency when it comes to estimating the development time.
Discuss
Answer: (b).By increasing the speed-up factor of the project Explanation:Shortening the development time means an increase in the number of people involved in the project. In terms of the Rayleigh curve model, shortening the development time amounts to an increase of the value a, the speed-up factor which determines the initial slope of the curve.
Q134.
According to Brooks' Law, what happens when manpower is added to a late project?
Discuss
Answer: (b).It makes the project later Explanation:Brooks' Law states that adding manpower to a late project only makes it later. This is because as the team size grows, communication overhead increases and new team members require time from other team members during their learning process, leading to a decrease in total productivity.
Q135.
What is the relationship between average productivity and average team size according to Conte et al.'s study?
Discuss
Answer: (b).Productivity decreases exponentially with team size Explanation:Conte et al.'s study found that average productivity (measured in lines of code per man-month) decreases exponentially with average team size. This can be explained by the increase in communication links required as team size grows, leading to a decrease in individual productivity.
Discuss
Answer: (c).The number of communication links increases as the team size increases Explanation:As team size increases, the number of communication links also increases, since each member needs to coordinate their activities with other members.
Discuss
Answer: (d).It increases the initial slope of the Rayleigh curve Explanation:Shortening the development time amounts to an increase of the value 'a', the speed-up factor which determines the initial slope of the Rayleigh curve. This causes a faster increase of manpower required at the start of the project and a higher maximum workforce.
Discuss
Answer: (b).It makes the project finish later Explanation:Adding manpower to a late project only makes it later, this is known as Brooks’ Law.
Discuss
Answer: (b).Productivity decreases exponentially with team size Explanation:According to Conte et al. (1986) the relationship between average productivity and average team size is L = 777P^(-0.5), which means that individual productivity decreases exponentially with team size.
Q140.
What is the maximum limit of shortening a software development project according to Boehm?
Discuss
Answer: (b).75% Explanation:Boehm sets the limit at 75% of the nominal development time, on empirical grounds. A system that has to be delivered too fast, gets into the ‘impossible region’. The chance of success becomes almost nil if the schedule is pressed too far.

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!