Risk Identification Techniques Quiz

Risk checklists, considering checklists of common categories that negatively impact on projects, and building checklists from corresponding requirements categories.

Missing or inadequate functionalities, safety hazards, security threats and vulnerabilities, reliability gaps concerning critical features, information inaccuracy, poor performance, unusability of features, or feature rejection by users.

Risk checklists can be specialized further along the taxonomy depicted in Section 1.15, as shown in Figure 15.

The generic risk of information inaccuracy, specifically related to the inaccuracy of train position/speed.

The awareness of possible risks impacting negatively on the objectives of the project is the prerequisite to risk control.

The awareness of possible risks impacting negatively on the objectives of the project.

Risk checklists.

Missing or inadequate functionalities, safety hazards, security threats, vulnerabilities, reliability gaps, information inaccuracy, poor performance, unusability of features, or feature rejection by users.

From task categories introduced in the text.

The generic risk of information inaccuracy related to the inaccuracy of train position/speed.

The components include the on-board train controller, the station computer, the train tracking system, the communication infrastructure, the acceleration controller, the doors controller, and track sensors.

Risk trees organize failures, causes, and consequences along causal links. They are used to identify risks through component inspection and can be made more systematic by organizing the information in a structured manner.

Fault trees are used when the failures relate to safety hazards. They are used to represent the logical combinations of events that can lead to a specific undesired event, in this case, safety hazards within the train control system.

Threat trees are used when the failures relate to security threats. They are used to represent the logical combinations of events that can lead to specific security threats within the train control system.

Figure 3.3 shows a simple fault tree for the train control system, representing the logical combinations of events that can lead to safety hazards within the system.

The Software Engineering Institute has elaborated a process oriented risk taxonomy together with a comprehensive list of questions.

Another risk-identification technique for product-related risks consists of reviewing the various components of the system-to-be.

For each component, we may determine what its possible failures are together with their respective causes and consequences.

Component inspection is a risk-identification technique for product-related risks.

The text mentions reviewing the various components of the system-to-be to determine possible failures, causes, and consequences as a risk-identification technique for product-related risks.

The Software Engineering Institute developed a process-oriented risk taxonomy and a comprehensive list of questions to help in spotting project-specific risks.

One of the considerations is to determine what the possible failures are together with their respective causes and consequences for each component of the system-to-be.

The text covers Boehm's list of top ten risks for product- and process-related risk categories.

The top ten risk categories listed by Boehm (1989) include product- and process-related risk categories.

The risk identification technique for product-related risks mentioned in the text consists of reviewing the various components of the system-to-be to determine possible failures, their causes, and consequences for each component.

The Software Engineering Institute has elaborated a process-oriented risk taxonomy along with a comprehensive list of questions for spotting project-specific risks.

According to the text, poor risk management leads to component inspection and the need to identify possible failures, causes, and consequences for each component of the system-to-be.