1.Why is the decomposition method necessary in software project estimation?
2.Which approach focuses on lessening the severity of a risk's consequences?
3.Which type of risk arises specifically from the software or hardware technologies employed in system development?
4.Which type of risk involves a purchased part not functioning as intended?
5.Which term best describes the level of uncertainty that a product will fulfill its specifications and be suitable for its intended purpose?
6.Which term most accurately describes a situation where the leadership of an organization shifts, bringing new priorities?
7.What type of risks arise due to limitations set by management or market conditions?
8.Which process involves methodically outlining potential threats to a project's plan?
9.Which type of risk endangers both the quality and schedule of the software development process?
10.Which of the following does not represent a business risk?
11.What type of risks relate to the total scale of the software being developed or changed?
12.Which type of risk poses a threat to the overall success of the software being developed?
13.What term describes the result of multiplying the likelihood of a loss occurring by the possible size of that loss?
14.What does the acronym COCOMO represent?
15.Which of the following is not considered a part of risk management processes?
16.Which estimation technique relies on empirically derived equations to forecast effort based on Lines of Code (LOC) or Function Points (FP)?
17.In which COCOMO model phase is it assumed that the software requirements are finalized and the fundamental architecture is defined?
18.Which approach was employed in the initial phases of software engineering to focus on prototyping user interfaces, analyzing software and system interactions, evaluating performance, and assessing the maturity of technologies?
19.Who was the original creator of the COCOMO model?
20.Where was the COCOMO-II model originally created?