Software Development Risk Research Articles

Group decision making using fuzzy sets theory for evaluating the rate of aggregative risk in software development

The purpose of this study is not only to build a group decision making structure model of risk in software development but also to propose two algorithms to tackle the rate of aggregative risk in a fuzzy environment by fuzzy sets theory during any phase of the life cycle. While evaluating the rate of aggregative risk, one may adjust or improve the weights or grades of the factors until she/he can accept it. Moreover, our result will be more objective and unbiased since it is generated by a group of evaluators.

Applying fuzzy set theory to evaluate the rate of aggregative risk in software development

The purpose of this study is not only to build a structure model of risk in software development but also evaluate the rate of aggregative risk by fuzzy set theory. While evaluating the rate of aggregative risk, we may adjust the weights or grades of the factors until we can accept it. We also show that the rate of aggregative risk is reasonable.

Toward an Assessment of Software Development Risk

Despite the introduction and use of a wide variety of system development methods and tools, software projects are still plagued by time and cost overruns, and unmet user requirements. To avoid these problems, it is frequently recommended that the risk associated with a software project be managed. A task that is critical to the proper management of software development risk is the assessment of the risks facing the project. Based on previous research, this paper proposes a definition and a measure of software development risk. Subsequently, data collected in a survey of 120 projects is used to assess the reliability and validity of the instrument.

Software Development Outsourcing Contract: Structure and Business Value

We address the case where a user contracts for the delivery of a new information system from an independent vendor, both of whom are risk-neutral. The delivery task is partitioned into two consecutive stages: system design and software development. The parties can contract for each stage separately or specify an initial contract that covers both stages. We compare the impact of different contracting structures on prices, project value, project completion probability, and the value to the developer of obtaining the first stage of the contract. Specifically, we show that a two-stage contracting can lead to a higher business value than stage-by-stage contracting. When there is competition for the design stage, the vendors bear more of the software development risk, and the probability the system will be completed depends on the contract structure.