Section: Volume B
Explanation
Explanation:
11.4.2.2 Quantitative Risk Analysis and Modeling Techniques page 337
Commonly used techniques use both event-oriented and project-oriented analysis approaches, including:
* Sensitivity analysis. Sensitivity analysis helps to determine which risks have the most potential impact on the project. It helps to understand how the variations in project's objectives correlate with variations in different uncertainties. Conversely, it examines the extent to which the uncertainty of each project element affects the objective being studied when all other uncertain elements are held at their baseline values. One typical display of sensitivity analysis is the tornado diagram (Figure 11-15), which is useful for comparing relative importance and impact of variables that have a high degree of uncertainty to those that are more stable.
The Tornado diagram is also helpful in analyzing risk-taking scenarios enabled on specific risks whose quantitative analysis highlights possible benefits greater than corresponding identified negative impacts. A tornado diagram is a special type of bar chart used in sensitivity analysis for comparing the relative importance of the variables. In a tornado diagram, the Y-axis contains each type of uncertainty at base values, and the X- axis contains the spread or correlation of the uncertainty to the studied output. In this figure, each uncertainty contains a horizontal bar and is ordered vertically to show uncertainties with a decreasing spread from the base values.

Section: Volume D
Explanation:
5.2.3.2 Requirements Traceability Matrix
The requirements traceability matrix is a grid that links product requirements from their origin to the deliverables that satisfy them. The implementation of a requirements traceability matrix helps ensure that each requirement adds business value by linking it to the business and project objectives. It provides a means to track requirements throughout the project life cycle, helping to ensure that requirements approved in the requirements documentation are delivered at the end of the project. Finally, it provides a structure for managing changes to the product scope.
Tracing includes, but is not limited to, tracing requirements for the following:
Business needs, opportunities, goals, and objectives;

Project objectives;

Project scope/WBS deliverables;

Product design;

Product development;

Test strategy and test scenarios; and

High-level requirements to more detailed requirements.

Attributes associated with each requirement can be recorded in the requirements traceability matrix. These attributes help to define key information about the requirement. Typical attributes used in the requirements traceability matrix may include: a unique identifier, a textual description of the requirement, the rationale for inclusion, owner, source, priority, version, current status (such as active, cancelled, deferred, added, approved, assigned, completed), and status date. Additional attributes to ensure that the requirement has met stakeholders' satisfaction may include stability, complexity, and acceptance criteria.
Process: 5.6 Control Scope
Definition: The process of monitoring the status of the project and product scope and managing changes to the scope baseline.
Key Benefit: The key benefit of this process is that it allows the scope baseline to be maintained throughout the project.
Inputs
1. Project management plan
2. Requirements documentation
3. Requirements traceability matrix
4. Work performance data
5. Organizational process assets
Tools & Techniques
1. Variance analysis
Outputs
1. Work performance information
2. Change requests
3. Project management plan updates
4. Project documents updates
5. Organizational process assets updates

Explanation/Reference:
Reference: https://mymanagementguide.com/project-knowledge-management-the-importance-of- managing-project-knowledge/