Assessing Overall Software Defect-Based Risk Using Analytic Hierarchy Process
Risk analysis and mitigation methods are gaining momentum among researchers and software professionals for preventing software project failures. It involves methods to deal with project uncertainties so that the project can become successful overcoming al
- PDF / 306,722 Bytes
- 12 Pages / 439.37 x 666.142 pts Page_size
- 43 Downloads / 262 Views
Abstract Risk analysis and mitigation methods are gaining momentum among researchers and software professionals for preventing software project failures. It involves methods to deal with project uncertainties so that the project can become successful overcoming all threats. In this context, determining the potential risk factors at each phase of software development lifecycle and relating those risks to the defects they produce is important. Analytic Hierarchy Process (AHP) is used to determine the priority of defects that leads to risk. AHP helps in assessing risk for each phase of an agile project. As agile models primarily help projects to accommodate change requests, and with each change request, a new risk items is generated, and AHP-based risk analysis becomes extremely relevant to agile software development. This paper investigates use of AHP for effective decision making to identify and remove defects. Weighted criteria are used for evaluating the decision. To implement meaningful weighted criteria, a case study is conducted among 20 software professionals with various experience levels. Total 35 potential risk source factor-based questions were evaluated according to Saaty’s scale. Keywords Risk · Mitigation · Priority · Defect · Scale · Weight
1 Introduction Software development projects are usually designed in stages, and each stage involves multiple activities. These activities are prone to risks. Several research papers on risk management in software projects have addressed the risk factors associated with the project [1]. If these factors are not identified early, then they can be held responsible P. Jha (B) Department of CS/IT, Amity University Jharkhand, Ranchi 834001, India e-mail: [email protected] K. S. Patnaik Department of CSE, BIT Mesra, Ranchi 835215, India e-mail: [email protected] © The Editor(s) (if applicable) and The Author(s), under exclusive license to Springer Nature Singapore Pte Ltd. 2021 V. Nath and J. K. Mandal (eds.), Proceedings of the Fourth International Conference on Microelectronics, Computing and Communication Systems, Lecture Notes in Electrical Engineering 673, https://doi.org/10.1007/978-981-15-5546-6_11
123
124
P. Jha and K. S. Patnaik
for the success or failure of the project. Various techniques of risk identification [2] and categorization [3–6] have been dealt along with analyzing the remedial approach. However, the fact that risk by nature is uncertain leaves the outcome of software projects to some element of chance. The relationship between software project performance and risks involved in it is iteratively examined during different phases of SDLC. It is advisable for all project managers to apply different risk mitigation strategies in order to avoid software project failure. Nowadays, the client requirements are changing frequently, therefore agile software development which involves dividing the entire project into miniprojects and trying to solve most risky elements first. Risk analysis helps in combating threats before they actually cause
Data Loading...
