All Free Software Engineering MCQs with Answers

• A. Two
• B. Three
• C. Four
• D. No form exists

Explanation: The traditional COCOMO model has three forms: Basic, Intermediate, and Detailed COCOMO.

• A. Function point sizing
• B. Change sizing
• C. Standard component sizing
• D. Fuzzy logic sizing

Explanation: Function point sizing estimates the software’s information-domain characteristics, such as inputs, outputs, inquiries, files, and…

• A. Software project estimation is a form of problem solving
• B. Developing a cost and effort estimate for a software project is too complex
• C. All of the mentioned
• D. None of the mentioned

Explanation: Software estimation is a complex problem-solving task, so decomposition breaks the project into smaller, more manageable components for…

• A. Avoidance strategies
• B. Minimization strategies
• C. Contingency plans
• D. All of the mentioned

Explanation: Minimization strategies reduce the probability or impact of a risk while allowing the project to continue.

• A. Managerial risks
• B. Technology risks
• C. Estimation risks
• D. Organizational risks

Explanation: Technology risks arise from the software, hardware, tools, or platforms used to develop and operate the system.

• A. Product risk
• B. Project risk
• C. Business risk
• D. Programming risk

Explanation: A purchased component that fails to perform as expected creates a product risk because it affects the capabilities or quality of the…

• A. Performance risk
• B. Cost risk
• C. Support risk
• D. Schedule risk

Explanation: Performance risk measures uncertainty about whether the product will satisfy its requirements and intended use.

• A. Staff turnover
• B. Technology change
• C. Management change
• D. Product competition

Explanation: A change in organizational leadership or management can introduce new priorities and alter project support, so it is a management change.

• A. Business impact risks
• B. Process definition risks
• C. Product size risks
• D. Development environment risks

Explanation: Business impact risks result from management decisions, market conditions, or business constraints that affect the project.

• A. Known risks
• B. Business risks
• C. Project risks
• D. Technical risks

Explanation: Technical risks can threaten both the quality of the software and the time needed to produce it, for example through unfamiliar technology…

• A. building an excellent product or system that no one really wants
• B. losing the support of senior management due to a change in focus or change in people
• C. lack of documented requirements or software scope
• D. losing budgetary or personnel commitment

Explanation: Lack of documented requirements or a clear software scope is a project or requirements-management problem, not a business risk.

• A. Business impact risks
• B. Process definition risks
• C. Product size risks
• D. Development environment risks

Explanation: Product size risks are associated with the scale of the software being built or modified, including its scope, complexity, and amount of…

• A. Known risks
• B. Business risks
• C. Project risks
• D. Technical risks

Explanation: Business risks threaten whether the software remains commercially viable, such as changes in the market, funding, or business strategy.

• A. Risk exposure
• B. Risk prioritization
• C. Risk analysis
• D. All of the mentioned

Explanation: Risk exposure is calculated as the probability of a loss multiplied by the magnitude of its potential impact.

• A. Constructive cost model
• B. Comprehensive cost model
• C. Constructive cost estimation model
• D. Complete cost estimation model

Explanation: COCOMO expands to Constructive Cost Model, an empirical model for estimating software development effort and cost.

• A. Risk assessment
• B. Risk generation
• C. Risk control
• D. None of the mentioned

Explanation: Risk assessment and risk control are recognized risk-management activities, whereas “risk generation” is not.

• A. FP-Based Estimation
• B. Process-Based Estimation
• C. COCOMO
• D. Both FP-Based Estimation and COCOMO

Explanation: Both FP-based estimation and COCOMO use empirically derived relationships to estimate effort from software size.

• A. Early design stage model
• B. Post-architecture-stage model
• C. Application composition model
• D. All of the mentioned

Explanation: The application composition model applies to the earliest stage, where prototyping, user-interface exploration, system interaction…

• A. B.Beizer
• B. Rajiv Gupta
• C. B.W.Bohem
• D. Gregg Rothermal

Explanation: Barry W. Boehm initially developed COCOMO, so option c is intended despite the misspelling “Bohem.” The model was introduced as an…

• A. University of Texas
• B. University of Southern California
• C. MIT
• D. IIT-Kanpur

Explanation: COCOMO II was developed at the University of Southern California’s Center for Software Engineering, associated with Barry Boehm.