Requirement Life Cycle Management in BABOK version 3

What is the first step in planning the Requirement Life Cycle?

• Create a project plan

• Gather and analyze the requirements

• Ignore the requirements

• Implement the requirements

Why is it important to identify stakeholders in the planning phase of Requirement Life Cycle Management?

• To minimize their involvement in the planning phase

• To understand their needs and expectations, and ensure their involvement in the requirement gathering process.

• To ignore their needs and expectations

• To exclude them from the requirement gathering process

What are the key components of a requirements management plan?

• Quality control, project management, supply chain

• Customer service, sales, human resources

• Software development, marketing, finance

• Stakeholder identification, requirements gathering and analysis, documentation, communication plan, change management process, and traceability matrix.

Explain the concept of traceability in Requirement Life Cycle Management.

• Traceability in Requirement Life Cycle Management is the ability to trace and track changes made to requirements throughout the entire life cycle.

• Traceability is the process of creating new requirements without tracking changes

• Traceability is not important in Requirement Life Cycle Management

• Traceability only tracks changes made to software code, not requirements

What are the benefits of conducting a feasibility study during the planning phase of Requirement Life Cycle Management?

• Conducting a feasibility study helps in creating unnecessary delays in the project

• Conducting a feasibility study helps in identifying potential risks, estimating costs, evaluating alternatives, and determining the viability of the project before investing time and resources.

• Conducting a feasibility study does not provide any valuable information

• Conducting a feasibility study only adds extra costs to the project

How can risk management be integrated into the planning of Requirement Life Cycle Management?

• By ignoring potential risks and focusing only on the positive outcomes

• By outsourcing risk management to a third-party company

• By waiting until the end of the requirement life cycle to address any potential risks

• By identifying potential risks at each stage of the requirement life cycle, assessing their impact, and developing mitigation strategies.

What are the different techniques for prioritizing requirements during the planning phase?

• Alphabetical order

• Some techniques for prioritizing requirements during the planning phase include MoSCoW method, Kano model, pairwise comparison, and cost-value prioritization.

• Random selection

• Customer feedback

Explain the concept of change control in Requirement Life Cycle Management.

• Change control is the process of only allowing changes to requirements at the end of the project

• Change control in Requirement Life Cycle Management is the process of managing and documenting changes to requirements throughout the project.

• Change control involves making changes to requirements without documentation

• Change control is the process of ignoring all changes to requirements

What are the key considerations for defining the scope of requirements in the planning phase?

• Not considering project constraints

• Identifying stakeholders, understanding project objectives, determining project constraints, and considering potential risks and dependencies.

• Ignoring stakeholders and project objectives

• Disregarding potential risks and dependencies

How can requirements be categorized and organized during the planning phase of Requirement Life Cycle Management?

• Alphabetically, numerically, by color, and by size

• By smell, taste, sound, and touch

• By priority, complexity, dependencies, and feasibility

• Randomly, haphazardly, without any order, and based on personal preference