Tangibility of Fuzzy Approach Risk Assessment in Distributed Software Development Projects

Abstract

Software is a product or a service or a project whose requirements are captured; specification document is prepared by requirements analysis; in/out architecture is designed; related source codes, variables, methods, classes, modules and relationships among these are written; necessary test and integration operations are done; when needed, maintenance, repair and update operations are executed by software or computer engineers and also that has its own documentation jobs and user manual, and has numeric and textual data, and also multimedia tools in its memory. Software development projects have a large financial burden and need to invest in high volumes. When looked at costs based on the international tangible data on computer software; it was $150 billion in 1985, it was $2 trillion in 2010 and it passed over $5 trillion after 2015. Also, in the year of 2018, the giro of Apple Store is about $250 million. Despite the costs, expenses and investments that are exponentially increasing every year, the rate of successful development of the software projects is not very high. Based on the “CHAOS” report (international size) prepared in 2016 only 17% of the software projects developed were completed in a timely manner, in the allocated budget and in accordance with the requirements. 53% of the projects were completed over time and/or over budget and/or also without fulfilling the requirements exactly. 30% of the software projects cannot have been completed in the development phase and were cancelled. For that software development projects with such high expenses and low success rate can have a better quality structure, a risk assessment approach has to be determined for the risk assessment methodology. So, some problems which may form software risks can be recognized and determined on time before causing trouble and endangering for software development projects. In this paper, some software risk assessment approaches underlying software risk management were introduced and explained in detail in addition to “fuzzy approach”. In addition, that this fuzzy technique is more useful and more effective for software risk evaluation in comparison with the others was showed and expressed by giving linguistic rules in this article. This paper tried to explain the terms from the general to the specific.