近些年，随着计算机互联网技术的迅猛发展，以及AI、大数据、云计算的盛行，软件的架构和技术也发生了日新月异的变化。软件的规模越来越大，功能的复杂度也越来越高，对可靠性、安全性、容错性、交互性、甚至是页面的灵动性都提出了更高的要求。在这种情况下，软件开发项目的风险变得更加难以控制，从而导致软件开发项目的频频失败，使得公司的利益受损。因此，针对软件开发项目的风险管理就显得特别的重要。

      本文先是从分析国内外软件开发项目风险管理的发展现状入手，探讨了国内外软件开发项目风险的识别、风险的评估以及风险的应对。其次，在软件开发项目风险管理理论和方法的基础上，结合B公司的Z软件项目的风险管理特点，探讨了Z软件开发项目的风险管理问题。第一阶段是风险的识别，本文用了WBS（工作分解结构法）对Z软件开发项目全生命周期上的工作进行了细致的分解，分解成一个个容易实现的节点，用头脑风暴法对每个工作节点上可能存在的风险进行了识别，得出一系列的风险条目，用德尔菲法对这些风险条目进行了梳理、总结以及归类，得出四大类风险（产品风险、开发风险、管理风险已经持续集成与部署风险）。第二阶段，进行风险分析，本文用RAC（风险评估指数法）对Z软件开发项目的风险进行了定性分析，通过创建风险的严重性等级表和可能性等级表，进而得出风险评估指数表，对每个风险条目的严重性和可能性进行打分，最终通过风险评估指数表过滤掉可忽略的风险条目。在RAC的基础上，用AHP（层次分析法）对Z软件开发项目的风险进行了定量的分析，通过构建层次结构递阶模型，计算出每条风险条目的权重，在通过一致性校验之后，根据权重对风险条目进行排序。第三阶段，根据风险的分析结果，针对不同权重的风险条目，分配不同的人力、资源和时间，给每个风险条目制定出具有针对性且行之有效的风险应对措施。最后，对B公司Z软件开发项目的风险管理研究进行了总结和展望。

      通过对B公司Z软件开发项目风险的识别、分析以及应对，使得B公司Z软件项目的风险管理达到显著的成效。成本比以往降低、项目进度在可控范围内、项目利益相关者的满意度也大幅度提升，同时也提高的公司的知名度。本文的研究，不但使B公司Z软件项目的风险管理达到期望，同时也为其它软件公司的软件开发项目风险管理提供了良好的借鉴作用。当然，随着技术的进步和软件开发项目管理方法的不断改变，软件开发项目中的风险管理也会不断演进。软件开发项目风险管理的方法虽然很多，但不是每一种方法都适用。项目团队的成员需要时刻保持敏锐的风险意识，灵活运用适合项目自身特点的风险管理方法，以应对不断变化的风险挑战，确保项目的成功交付。

In recent years, with the rapid development of computer internet technology and the prevalence of AI, big data, and cloud computing, the architecture and technology of software have also undergone rapid changes. The scale of software is increasing, and the complexity of its functions is also increasing, which puts forward higher requirements for reliability, security, fault tolerance, interactivity, and even page flexibility. In this situation, the risks of software development projects become more difficult to control, leading to frequent failures of software development projects and damaging the company's interests. Therefore, risk management for software development projects is particularly important.

 

This article starts with analyzing the current development status of risk management in software development projects both domestically and internationally, and explores the identification, assessment, and response of risks in software development projects both domestically and internationally. Secondly, based on the theory and methods of software development project risk management, combined with the risk management characteristics of Company B's Z software project, this paper explores the risk management issues of Z software development projects. The first stage is risk identification. This article uses WBS (Work Breakdown Structure Method) to carefully decompose the work throughout the entire lifecycle of the Z software development project, breaking it down into easily achievable nodes. The brainstorming method is used to identify potential risks at each work node, resulting in a series of risk items. The Delphi method is used to sort, summarize, and classify these risk items, Identify four major types of risks (product risk, development risk, and management risk that have been continuously integrated and deployed). In the second stage, risk analysis was conducted. This article used RAC (Risk Assessment Index Method) to qualitatively analyze the risks of the Z software development project. By creating a severity level table and a possibility level table of the risks, a risk assessment index table was obtained. The severity and likelihood of each risk item were scored, and finally, negligible risk items were filtered out through the risk assessment index table. On the basis of RAC, the risk of Z software development project was quantitatively analyzed using Analytic Hierarchy Process (AHP). By constructing a hierarchical model, the weight of each risk item was calculated. After consistency verification, the risk items were sorted according to the weight. In the third stage, based on the analysis results of risks, allocate different manpower, resources, and time for risk items with different weights, and develop targeted and effective risk response measures for each risk item. Finally, a summary and outlook were made on the risk management research of Company B's Z software development project.

 

By identifying, analyzing, and responding to the risks of Company B's Z software development project, the risk management of Company B's Z software project has achieved significant results. The cost has decreased compared to before, the project progress is within a controllable range, and the satisfaction of project stakeholders has significantly increased, while also increasing the company's visibility. The research in this article not only meets the risk management expectations of Company B's Z software project, but also provides a good reference for the risk management of software development projects in other software companies. Of course, with the advancement of technology and the continuous changes in software development project management methods, risk management in software development projects will also continue to evolve. Although there are many methods for risk management in software development projects, not every one is applicable. Members of the project team need to maintain a keen risk awareness at all times and flexibly apply risk management methods that are suitable for the project's own characteristics to cope with constantly changing risk challenges and ensure the successful delivery of the project.

[1]Barry Boehm, Software risk management[J]. Lecture Notes in Computer Science,1989,387(1).
[2]Fan C,Yu Y. BBN-based software project risk management[J]. The Journal of Systems & Software,2003,73(2).
[3]Singh V. A Simulation-Based Approach to Software Project Risk Management[J]. Asia Pacific Business Review,2008,4(1)..
[4]Cui W,Ye J,Lin Y, et al. Japan Software Project Risk Management[J]. Advanced Materials Research,2011,1286(267-267).
[5]Elzamly A,Hussin B. Mitigating Software Maintenance Project Risks with Stepwise Regression Analysis Techniques[J]. Journal of Modern Mathematics Frontier,2014,3(2).
[6]Abeselom M T,Ernest M. Software Project Risk Management Practice in Ethiopia[J]. The Electronic Journal of Information Systems in Developing Countries,2017,79(1).
[7]林新洁, 吴昌荣, & 张铭. 软件开发过程中风险识别与管理[J] 计算机工程与科学, 2019 41（05）, 811-817.
[8]葛浩文, & 李柏青. 基于生命周期的软件开发风险管理研究[J]电脑知识与技术, 2019（01）, 1-3.
[9]Rahman & Keung, A Systematic Review of Risk Identification Techniques for Software Intensive Systems[J]. International Journal of Advanced Computer Science and Applications, 2012,12（6）.
[10]El-Sheikh et al., A Systematic Review of Risk Identification Techniques for Software Project Risk Management[J]. Sustainability, 2014,12（23）.
[11]Santos et al., Risk Identification in Requirements Engineering: A Survey[J]. Enterprise Information Systems,2015,14（6）.
[12]Andrade et al., A Systematic Review of Risk Identification in Agile Projects[J]. Información tecnológica,2017,31（3）.
[13]Ali et al., Risk Identification in Global Software Development: A Systematic Literature Review[J]. Journal of Computational and Theoretical Nanoscience,2018,17（2）.
[14]邓世杰, 李守波, & 刘敏. 基于精细度技术的软件开发风险识别方法研究[J]. 高科技与产业化, 2018. 176（5）, 62-65.
[15]余蓉, 郑锐, & 贾琳. 基于贝叶斯网络的软件开发风险识别方法[J]. 计算机应用与软件, 2019. 36（3）, 120-125.
[16]Sommerville & Tully, A Review of Software Risk Analysis Methods and Techniques[J]. Technology News Focus,2010.
[17]Kocaguneli et al., Software Risk Analysis in the Real World: A Comparison of Agile and Traditional Approaches[J]. IET Software,2012,13（3）.
[18]Hosein et al., A Systematic Review of Risk Assessment Methods for Software System Development[J]. International Journal of Innovative Technology and Exploring Engineering （IJITEE）,2013,8（7）.
[19]Riaz et al., A Systematic Review of Software Risk Analysis Methods and Their Applications[J]. International Journal of Advanced Networking and Applications,2014,10（SP5）.
[20]Pinto et al., A Systematic Review of Risk Analysis Techniques in Software Engineering[J]. Complex Systems Informatics and Modeling Quarterly,2018（15）.
[21]Korhonen et al., A Systematic Review of Software Risk Analysis Techniques for Safety-Critical Systems[J]. International Journal of Advanced Computer Science and Applications （IJACSA）,2019,9.
[22]苏洁, 张升华, & 张蕾. 基于AHP算法的软件开发风险分析模型[J]. 计算机应用, 2018. 38（06）, 1696-1701.
[23]李东升, 钟丹娜, & 唐杰. 软件开发风险分析方法的研究进展[J]. 软件工程, 2020.（07）, 35-39.
[24]Salleh et al., A Review of Risk Response Strategies in Software Engineering Projects[J]. International Journal of Software Engineering & Applications,2012,9（2）.
[25]Ruiz et al., Risk Response Strategies in Software Engineering: A Systematic Literature Review[J]. Global Sci-Tech,2013,10（4）.
[26]Azeem et al., A Systematic Review of Risk Response Techniques for Large-Scale Software Development Projects[J]. Management : Journal of Contemporary Management Issues,2014.
[27]Ruiz et al., A Systematic Review of Risk Response Techniques for Software Intensive Systems[J]. Journal of Engineering,2015.
[28]Sharma et al., Risk Response Strategies in Agile Software Development: An Empirical Investigation[J]. IEEE Access,2017,5.
[29]Imani et al., A Systematic Review of Risk Mitigation Techniques for Software Development Projects[J]. International Journal of Computer （IJC）,2019,20（1）.
[30]杨文秀, 秦勇, & 边熠. 基于风险管理的软件开发过程控制方法[J]. 水电能源科学, 2019. 37（4）, 73-77.
[31]王聪, 魏阳, & 宋增. 基于多属性决策的软件开发风险应对模型[J].价值工程, 2021. 40（07）, 393-396.