Question

请翻译成中文，谢谢！！（不要软件翻译）

3 Extracted Risks from the Issues and Concerns Table
Prior to this research, we first obtained a list of issues and concerns described by project members of an actual software development project. Then we extracted risks from the list to see what kinds of risks exist in an actual project. Other than potential risks, the list also contains memos and the description of problems that already happened. Since the purpose of this research is to know what kinds of risks exist in a project, we considered following points when we check the issues and concerns in the list. Points considered are as follows;
- Repeated issues and concerns were counted once.
- Technical issues and concerns found in tests and trial procedures were eliminated except typical one.
- Notes and memos were eliminated as they are not recognized as risks.
From the documents from the issues and concerns list, there are 25 risks were extracted as a result of the risk extraction. Table 1 shows the risks. The issues and concerns list are described only from engineers’ perspectives. To make the list of risks more comprehensive, we considered some additional perspectives such as occupational health and safety, human behavior and crime control. After that, total 38 risks were extracted as a result.
4 Analyzes of Risk Factors
Next, we reviewed these risks and analyzed their causes by using the affinity diagram.Figure 1 shows the analysis procedure.
Thinking about the causes of risks in Figure 1, we found that the causes of risks were categorized into two causes; one is the cause rooted in the project components, and another is the cause rooted in fundamental causes of risks or mechanism of risk occurrence. Moreover, we found that each risk description always involves those two elements, project components and fundamental causes of risks. For Example, in case of “Potential shortage of disk drive space”, “space” or “disk drive space” is corresponding to “project components”. “Potential shortage” is corresponding to “fundamental causes of risks”. In other words, it can be addressed as “More space might be needed than planed”. Table 2 shows the analysis of causes of risks by using affinity diagram [4]. As b) shows, the situation of “More space might be needed than planed” could be caused by the gap between the initial plan and the actual result.
Every project has a plan. If the project plan was perfect and project was assured to be executed just as the plan, there would be no risks except failures, errors and external factor. But there is no project that is free from assumptions and assumptions always contain uncertainty. Uncertainty could cause gaps between the plan and the actual result. This is one of the major reasons why every project has risks.

Answer 1

3提取风险问题和关系表
在此研究之前,我们先取得一系列问题和项目成员提供了一个实际软件开发项目。然后我们提取风险从名单上看到什么样的风险存在于一个实际的项目。除了潜在风险,这些名单中也包括备忘录和描述的问题已经发生了。因为这项研究的目的是知道什么样的风险存在于一个项目,我们认为以下几点问题和我们检查列表的内容。分考虑如下;
——重复问题和被数一次。
发现-技术问题和检测和试验程序消除除典型之一。
——纸币和备忘录被消除,因为他们并不是公认的风险。
从问题的关切和文件列表,有25个风险提取结果的风险提取。表1显示了风险。名单上的问题和阐述的观点仅从工程师。使风险更全面的名单,我们认为另外一些方面职业健康和安全、人类行为和打击犯罪。在那之后,总38风险提取的结果。
4的危险因素。分析了
接下来,我们回顾了这些风险,深入分析了其产生的亲和力,运用图表。图1中指出了分析程序。
考虑风险的原因在图1中,我们发现风险的原因分为两个原因;一个是导致根植于项目组成,另一个是事业植根于的根本原因或机理发生风险的风险。此外,我们发现每个风险描述这两个因素通常会涉及到组件和根本原因,项目的风险。例如,在“潜在短缺的情况下硬盘空间”,“空间”或“硬盘空间”是对应于“项目”,“潜在劳动力短缺部件”是相应的t