浅析软件开发项目过程中的风险管理

软件项目开发中存在的各类风险会影响项目计划的实现,如果项目风险变成现实,就有可能影响项目的进度,增加项目的成本,甚至使软件项目不能实现。成功的项目管理一般都对项目风险进行了良好的管理。该文就软件开发项目过程中存在的风险进行分析,并比较了几种主流的风险管理模型,探讨如何对项目进行有效的风险管理,从而最大限度的减少风险的发生。     

软件项目风险管理研究

进行大型的软件项目开发过程中,由于种种难以预见的不确定性因素,会给软件项目带来造成失败的风险.首先介绍了软件风险的基本概念,分析了软件项目风险的特点,以及如何识别软件风险.对项目管理中的风险分析、风险管理进行了详细地探讨,提出对风险进行量化管理.最后对软件开发过程中各阶段的风险进行了分析和研究,给出了减轻或防止风险发生的几种方法.研究软件项目风险管理对于软件开发、软件项目管理及软件产品质量都具有重要意义.     

一种改进的软件项目开发风险管理模型

该文提出了一种改进的软件项目开发风险管理模型。该模型在贝叶斯网络的建模过程中以样本数据集为基础进行结构学习和参数学习,建立更符合实际软件项目特征的贝叶斯网络。同时,进一步完善了软件项目开发风险管理流程,并利用贝叶斯网络的信念更新过程实现动态软件项目风险管理。经实践检验,该改进模型能够更有效地对软件项目开发过程中的风险进行管理,提高软件开发的成功率。     

基于贝叶斯网络的软件项目风险管理模型

提出了一种基于贝叶斯网络的软件项目风险管理模型。随着软件项目的进行,该风险管理模型能够利用不断更新的项目数据持续地预测潜在风险,确定风险源并采取适当的应对措施降低风险发生概率。经实践检验,在软件开发过程中引入该风险管理模型能够有效地对风险进行管理,提高软件开发的成功率。     

一种基于贝叶斯网络的软件项目风险管理方法

提出一种新的软件项目风险管理方法,采用贝叶斯网络同时对风险发生概率和风险影响进行推理.该风险管理方法能够随着软件项目的进行持续地评估潜在风险,并采取适当的措施应对风险.实践证明,在软件开发过程中引入该风险管理方法能够有效地对风险进行管理,提高软件开发的成功率.     

软件项目的进度风险管理

文章介绍了软件项目中风险与风险管理的概念和一般过程，重点讨论了如何使用RE法对软件项目进度风险进行风险评估、优先级排序，从而有效地控制软件项目进度风险。     

浅析中小软件项目开发的风险管理

本文从风险管理的角度,对中小软件项目开发中存在的问题进行了分析,提出中小软件开发过程中应建立适度的风险管理机制．遵循风险管理要求的”风险识别”、”风险分析”、”风险应对”的步骤,时潜在和已经发生的项目风险进行有效管理和控制。     

谈软件项目风险管理

软件项目的风险管理是项目成功与否的关键。本文概述了软件项目的风险,讨论了进行风险管理的意义、风险管理的步骤及一些方法,最后就改进我国目前软件项目风险管理现状提出几点建议。     

降低软件项目风险的方法研究

在分析软件项目风险成因的基础上,对项目管理中的风险分析、风险管理进行了详细的研究,提出了软件项目风险的量化管理和降低软件项目风险性的方法。该方法有助于软件项目管理者更好地理解潜在的主要风险因素,从而进行更好的风险管理。     

软件风险管理的数据库模型

风险管理是软件项目开发过程中一个关键过程域,直接影响到软件的质量、进度及资金投入,决定项目的成败。目前,风险管理原始数据从本质上来源于领域专家已有经验,具有较大的主观性,并且各个项目开发客观条件都不尽相同,不能完全借鉴。本文从风险管理过程出发,总结CMMI软件风险管理模型,建立风险管理数据库模型,将不断修正的数据积累值作为软件风险的识别标准,以保证风险识别的客观性。     

软件项目风险管理综述

风险在软件开发过程中无处不在,如何控制软件项目中出现的各种风险一直是软件工程领域研究的主要问题之一软件开发过程方法对控制软件风险有积极的作用,RUP、CMM等方法对软件项目风险有着良好的控制能力很多学者都使用不同的方法或技术对软件项目风险进行分析或管理。     

Exploring the relationship between software project duration and risk exposure: A cluster analysis

Software projects often fail. Thus it is important to find ways to ensure a successful outcome. One significant area is a better understanding of the relationship between the software project duration and risk exposure, as this helps project managers with pertinent information to be effective in managing risky projects. We addressed this need by adopting a cluster analysis technique to provide managers with insight into effective planning and control of their projects. The results not only revealed that risk exposures associated with user, requirement, planning & control and team risk dimensions were affected by project duration, but also showed how to manage software risks effectively through observing trends in the risk components. Based on our findings, project managers can adopt appropriate attitudes, skills, and practices to deal with risky areas more effectively rather than just identifying those software risks with which project managers should be concerned.     

An empirical study on the implementation and evaluation of a goal-driven software development risk management model

ContextBuilding a quality software product in the shortest possible time to satisfy the global market demand gives an enterprise a competitive advantage. However, uncertainties and risks exist at every stage of a software development project. These can have an extremely high influence on the success of the final software product. Early risk management practice is effective to manage such risks and contributes effectively towards the project success.ObjectiveDespite risk management approaches, a detailed guideline that explains where to integrate risk management activities into the project is still missing. Little effort has been directed towards the evaluation of the overall impact of a risk management method. We present a Goal-driven Software Development Risk Management Model (GSRM) and its explicit integration into the requirements engineering phase and an empirical investigation result of applying GSRM into a project.MethodWe combine the case study method with action research so that the results from the case study directly contribute to manage the studied project risks and to identify ways to improve the proposed methodology. The data is collected from multiple sources and analysed both in a qualitative and quantitative way.ResultsWhen risk factors are beyond the control of the project manager and project environment, it is difficult to control these risks. The project scope affects all the dimensions of risk. GSRM is a reasonable risk management method that can be employed in an industrial context. The study results have been compared against other study results in order to generalise findings and identify contextual factors.ConclusionA formal early stage risk management practice provides early warning related to the problems that exists in a project, and it contributes to the overall project success. It is not necessary to always consider budget and schedule constraints as top priority. There exist issues such as requirements, change management, and user satisfaction which can influence these constraints.     

企业信息化项目的风险管理

信息化项目的风险管理决定了整个项目甚至整个企业信息化建设的成败,本文对信息化项目所面临的风险进行分析调研,并提出行之有效的风险管理措施,旨在帮助企业正确合理地应对信息化项目所面临的风险,从而保障企业信息化建设的顺利开展。     

An Empirical Approach to Characterizing Risky Software Projects Based on Logistic Regression Analysis

During software development, projects often experience risky situations. If projects fail to detect such risks, they may exhibit confused behavior. In this paper, we propose a new scheme for characterization of the level of confusion exhibited by projects based on an empirical questionnaire. First, we designed a questionnaire from five project viewpoints, requirements, estimates, planning, team organization, and project management activities. Each of these viewpoints was assessed using questions in which experience and knowledge of software risks are determined. Secondly, we classify projects into “confused” and “not confused,” using the resulting metrics data. We thirdly analyzed the relationship between responses to the questionnaire and the degree of confusion of the projects using logistic regression analysis and constructing a model to characterize confused projects. The experimental result used actual project data shows that 28 projects out of 32 were characterized correctly. As a result, we concluded that the characterization of confused projects was successful. Furthermore, we applied the constructed model to data from other projects in order to detect risky projects. The result of the application of this concept showed that 7 out of 8 projects were classified correctly. Therefore, we concluded that the proposed scheme is also applicable to the detection of risky projects.     

Investigating software testing and maintenance reports: Case study

ContextAlthough many papers have been published on software development and defect prediction techniques, problem reports in real projects quite often differ from those described in the literature. Hence, there is still a need for deeper exploration of case studies from industry.ObjectiveThe aim of this study is to present the impact of fine-grained problem reports on improving evaluation of testing and maintenance processes. It is targeted at projects involving several releases and complex schemes of problem handling. This is based on our experience gained while monitoring several commercial projects.MethodExtracting certain features from detailed problem reports, we derive various measures and present analysis models which characterize and visualize the effectiveness of testing and problem resolution processes. The considered reports describe types of problems (e.g. defects), their locations in project versions and software modules, ways of their resolution, etc. The performed analysis is related to eleven projects developed in the same company. This study is an exploratory research with some explanatory features. Moreover, having identified some drawbacks, we present extensions of problem reports and their analysis which have been verified in another industrial case study project.ResultsFine-grained (accurate) problem handling reports provide a wider scope of possible measures to assess the relevant development processes. This is helpful in controlling single projects (local perspective) as well as in managing these processes in the whole company (global perspective).ConclusionDetailed problem handling reports extend the space and quality of statistical analysis, they provide significant enhancement in evaluation and refinement of software development processes as well as in reliability prediction.     

Choquet integral based aggregation approach to software development risk assessment

Software is a crucial component of today’s business environment, and a superior risk management effort is required to adeptly steer software development projects. Software development risks are inherently dependent, in other words, mutually positive or negative assessments of some risks can influence the decision to accept or reject a project. This fact cannot be modeled with a traditional best compromise seeking method. Aggregation operations based on the family of fuzzy integrals include many operators and thus can express a variety of decision maker behaviors. This study proposes an integrated multi-criteria evaluation methodology for software development experts and managers to better enable them to position their projects in terms of the associated risks. The method relies on a special fuzzy operator, namely a two-additive Choquet integral that enables modeling various effects of importance and interactions among risks. The potential of the proposed methodology is exposed through a case study conducted in a Turkish software company.     

软件质量量化指标及实现方法的探讨

在ISO软件质量模型的基础上,建立质量需求评价准则(SQRC)和质量设计评价准则(SQDC)之间的定量关系,将软件质量需求指标转化为软件质量的设计指标,为软件开发人员在设计和编码阶段实施软件质量保证提供指南。它将软件质量保证的任务向设计和编码人员进行分解,有利于软件项目工程化生产过程中的质量管理,从而降低软件生产的风险。     

SOFTLIB — a documentation management system

This paper describes a software sysem (SOFTLIB) that has been developed to assist in the management of software documentation generated during systems development projects. It provides facilities to manage large numbers of documents, to file documents when they are complete and to issue them to system developers and maintainers. It also includes an information retrieval facility that allows programming staff to find documents, to examine their contents before issue and to assess the state of the software project documentation. SOFTLIB is explicitly intended to help manage the documentation generated during software development — it is not designed for use by end-users of that software or for managing end-user documentation. The novel characteristic of this system is the approach that is taken to the consistency and completeness of documentation. The documentation associated with a software system is organized in such a way that it may be detected if document sets are complete (that is, if all documentation which should be provided for a software component is available) and if document sets are likely to be inconsistent. This means that if a document has been changed without a comparable change being made to other associated documents, this is detectable by the librarian system. In addition, a subsidiary aim of our work was to investigate the utility of menu systems to complex software tools by building a user interface to SOFTLIB. We conclude that menu systems are far from ideal in such situations because of the range of possible options which must be handled by the system.