Risk Identification

Correct Answer: Historical Analysis

Given the scenario, the risk identification method most likely utilized is Historical Analysis. This approach involves using data and experience from earlier similar projects to identify risks in the current project. Here, high-force winds in a hurricane-prone area related to the durability of a high-rise building structure would have been a situation that has occurred in the past. Thus, through historical analysis, this risk is identified for the current project. This is why the other answers are incorrect: Brainstorming is a creative problem-solving method that involves the generation of ideas by a group, this method may or may not identify this particular risk without the context of historical project experiences. The Delphi Technique involves a group of experts who anonymously reply to questionnaires and subsequently receive feedback in the form of the group response, aiming at a consensus. This would not necessarily provide concrete data-based risk identification as provided by historical analysis. SWOT Analysis is used to identify Strengths, Weaknesses, Opportunities, and Threats; it's a strategic planning tool more than a risk identification one.

Correct Answer: Technical reviews

In this scenario, the best suited risk identification technique is 'Technical reviews'. Technical reviews involve a thorough examination of the software's code, design and integration, which allows for early detection of any potential issues or flaws that might lead to security risks. The main focus here is to identify any coding errors that could compromise the software's security hence 'Technical reviews' are the most viable options. In contrast, other techniques such as 'Brainstorming', 'Interviewing' and 'Checklist analysis' can also identify risks, but they are less effective in this particular situation as they rely more on theoretical aspects or focus on more general aspects of the project rather than technical details. 'Brainstorming' is primarily used for generating ideas and is less about identifying specific technical risks. 'Interviewing' is often more focused on understanding people's perspectives or skills, rather than the technical aspects of the system. 'Checklist analysis' might overlook this intricate detail as it involves going through a predefined list of common risks, whereas this situation requires a deep understanding of less frequent but highly impactful risks like a coding error that could lead to a significant security flaw.

Correct Answer: From past experiences with different projects

The risk of lack of user acceptance due to unfamiliarity with the system was most likely identified from past experiences with different projects. Organizations often rely on lessons learned from previous implementations to anticipate potential risks in new projects. In ERP system implementations, user resistance is a common issue observed in past projects, especially when users are introduced to new systems that alter their usual workflows. By reflecting on these past experiences, the project team can proactively identify and address such risks to ensure a smoother adoption process.